Okay @craineum we had a lengthy discussion in our last core team meeting. One concern was the experience of generating 30+ new files and overloading new devs. People are already a little overwhelmed that we create so many as it is, we’re worried that tripling that amount is going to be a lot to handle. We talked about maybe prompting when creating a scaffold, asking if you also want to generate tests and stories, or maybe just compressing the file list somehow so it isn’t so long. Or, update the post-install instructions with a more friendly overview of what was created so you’re not just handed 50 files and being told “good luck!”
There was also a discussion of how much the web side tests are actually used…since all the business logic should be living in your services, api tests seemed more important, and run more frequently. Do you find that’s the case, or are you running the entire suite most of the time?
There was also an idea to just generate tests for the “important” functions, like submitting the form, with good and bad data. Most of the pages that are created just show a cell, so t he pages themselves wouldn’t necessarily need tests. How do you feel about only some files having tests and not others?
Is your concern with missing tests/stories that you actually do keep those scaffolded pages around as admin pages, and want to make sure they don’t break if a DB field is removed, for example? Are you heavily modifying them and want to make sure they stay tested? Are you a completionist and it just feels wrong not to have them? haha
We’re going to shop these same questions around with some teams we’re in contact with that are creating startups using Redwood to hear if/how they’re using scaffolds and how they feel about the lack of tests on the web site.
Sorry this took so long to get an answer that isn’t really an answer yet, but we’re definitely giving it serious consideration!