add a simple test runner?
See original GitHub issueAn important target group for this app (imo) are beginners and prototype builders. From my experience, both these groups would benefit greatly from having simple test infrastructure bundled with this starter.
From my own experience, I usually have a script.js that I’d include into the main module, but that’s pretty hacky until I finally setup (whatever flavor of test infra is popular). The value I get is from being able to write code that’ll run on every edit-save separately from my app, but that later morphs into a unit test suite or so on. For beginners, they’d build their app, but write tests for smaller parts of the app they’re building, while learning to write tests for their code.
To be clear, I’m not advocating any specific framework/suite/assert libs; I’d just like to be able to run even a if(true) throw new Error
script on every change.
Thoughts?
Thanks for the great tool!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:12
- Comments:51 (25 by maintainers)
Top GitHub Comments
Huge vote for Mocha + Enzyme + Sinon. This probably requires JSdom, at least according to Enzyme docs.
I’d err on the side of having
__tests__
folders anywhere in the tree. It’s very painful to write imports that go many folders up and then many folders down. Also colocating related code helps comprehension.