I have the strong impression that the current chapter for testing in the meteor guide (https://github.com/meteor/guide/blob/master/content/testing.md) does not really reflect how the community here does testing.
The current testing chapter mentions some outdated frameworks and leaves out mentioning a lot which I found by a research - https://github.com/meteor/guide/issues/888 and https://github.com/meteor/guide/issues/672 are two examples.
The main testing framework currently seems to be mocha. The docs there need to be improved https://github.com/meteortesting/meteor-mocha/issues/80 but there’s also https://github.com/cult-of-coders/meteor-mocha which is a fork of https://github.com/practicalmeteor/meteor-mocha, making it usable for Meteor 1.6.x and newer, making it possible to show the results of both server and client tests in the browser. @diaconutheodor would be nice if you would join the conversation.
On the other side I also found some people playing around with
Jest (https://blog.meteor.com/real-world-unit-tests-with-meteor-and-jest-3d557e84e84a, https://www.npmjs.com/package/jest-meteor-stubs) which I mainly started looking into because they support snapshot testing (https://jestjs.io/docs/en/snapshot-testing). It could be that this also is more suited for creating unit-tests, I don’t know. @rdickert, I also want you to join, because you wrote the article.
What do you use? Which is (as of your opinion) the better choice to take and should be included (removed, replaced, updated, kept) in the guide?
When I see this thread settling, I’ll create a PR to the repository of the guide.
This thread is meant as a fork of Testing guide article - providing a place to discuss which of the frameworks the testing-guide should include.
- Mocha (meteortesting)
- Mocha (cult-of-coders)
- Mocha (practicalmeteor)
- Mocha (dispatch)
- Mocha (other)
- Jasmine (sanjo)
- Other (please explain)