Easily stub out Meteor collections with in-memory local collections. The idea here is to allow the use of things like Factories for unit tests and styleguides without having to restrict ourselves to making components "pure". So a component (ie. a template) can still call Widgets.findOne(widgetId), it's just that we will have stubbed out Widgets to point to a local collection that we can completely control in our test.
meteor add hwillson:stub-collections// client or server
import StubCollections from 'meteor/hwillson:stub-collections';StubCollections.add([collection1, collection2, ...]) - register the default list of collections to stub.StubCollections.stub() - stub all collections that have been previously enabled for stubbing via add().StubCollections.stub([collection1, collection2, ...]) - stub a specific list of collections, overriding the list registered via add().StubCollections.restore() - undo stubbing (call at the end of tests, on routing away, etc.)See this packages tests.
This project was originally created by MDG, and shipped with the Meteor Guide's todos reference application (thanks MDG!). If you have any questions/comments, open an issue here.
sinon to avoid timeouts (#30 - thanks @sebakerckhof!).direct accessors were not properly stubbed (thanks @zeroasterisk!).add (PR #18 - thanks @Floriferous!).underscorepracticalmeteor:mocha with meteortesting:mochasinon and chai packages