Look into better setup for testing

[jehoshua02]

My TDD pain points:

• [x] Jest + React + Webpack preprocessing: I want to process files the same way I do during build right? Resolved using babel-jest. Compiles jsx in tests and loaded modules.
• [x] ~~tests: I would like 'tests', and to be able to nest test related stuff in there to without jest picking it up and treating it like a test.~~ I conform to the convention established by jest. Adding underscores moves the directory to the top of the list alphabetically, making it more visible, making it stand out more, and thereby promoting test driven development, a skill I want more developers to practice.
• [x] module paths: I like to structure tests to mirror app but I don't like '../../../../../../some/path/to/module/ugh'. I would like 'app/components/MyComponent'. This also makes things clean for jest.dontMock('module/path').
• [ ] coverage: Since adding in babel-jest, running tests with --coverage option is throwing a big ugly error. Issue reported with babel-jest and jest-cli. Coverage is output to the console so I'm happy, but I wish I could disable whatever is throwing the error (I'm assuming whatever is writing to disk).
• [ ] mocking reflux actions: I want to test that a component calls a reflux action like it should after user interaction. But it doesn't seem to be working. I've submitted an issue on my react project as well as over at jest.
• [ ] Take a look at Karma. I really like the idea of testing (not just integration/ui/end-to-end, but unit as well) in real browsers and not just node.

[jehoshua02]

@nhunzaker recommended Karma. I like the idea of testing in real browsers. He gave me this link: https://github.com/nhunzaker/webpack-boilerplate

[jehoshua02]

Got this working: https://github.com/jehoshua02/react-scaffold/pull/11

[jehoshua02]

But it doesn't work with coverage.

[jehoshua02]

Closing in favor of smaller more focused issues.