I mean that practicalmeteor:mocha is a package testing solution only (as things currently stand). It does not work for app-testing. The new changes from the MDG will replace Velocity’s “mirrors” with an app-testing mode.
Once this app testing mode is ready, it will allow for tools like the current mike:mocha or sanjo:jasmine to be ported over from Velocity. I’m not sure if the MDG will actually do something here or not, that’s not too clear to me yet.
As for unit testing, with 1.3 modules you no longer need to load the entire Meteor context. There’s already an example to do that here: