Recently the Velocity project was handed back to MDG, which we know are very busy.
This may cause concern for the testability of Meteor but after watching the talk “How to Stop Hating your Test Suite” i’m pretty convinced that this is the way forward for Meteor testing in the next year. Perhaps the built in integration testing will improve soon.
Spoiler alert… In the talk it boils down to writing less integration tests and focuses more on unit tests and end-to-end tests.
Use integration testing sparingly because they make the same exact test test time grow exponentially as your project grows even if that test hasn’t changed (due to setup and teardown).
This means that we’re in pretty great shape actually! Unit tests run very fast because we can run them outside of Meteor & Velocity. Jasmine for example can stub a
Meteor.userId and return a value. I’ve done this with 2 projects with a lot of success.