-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testing recommendation #24
Comments
Mocha is a great tool. I use tape. Mocha is valid but not everybody wants to standardize on a test framework. |
yeah sorry, I was probably a little confusing. I threw out the example of On Thu, Mar 17, 2016 at 3:32 PM, Peter Moresi [email protected]
|
a coworker just showed me how in test, he uses a webpack dev server configured exactly the same as development except that it doesn't include the app entrypoint -- and then karma runs the test file(s) itself and depends on that webpack bundle. so the question I've yet to answer: is it useful (in a test framework independent way, per @petermoresi's comment) to bake-in the building of that test asset to rwb? |
I think it'd be cool to have some sort of recommendation around testing. Since the build tool bullshit lives in rwb, it seems we could benefit from a bit of coordination to reuse it all for tests.
As a concrete example, here's what I've started within my own rwb project. I like enzyme and mocha, and I like fast tests so I opted for the node flavor rather than karma, etc. But this means I need to babel myself, stub out webpack CSS requires (which is naive and will certainly break), and generally do things that follow a different flow than my production code will.
install deps
package.json
mocha-compilers.js
MyComponent.test.js
Thoughts on how we could make this better? I'm happy to work on a PR once there's a plan.
The text was updated successfully, but these errors were encountered: