Separate Client from Server Unit Tests (enhancement)

[Nomeasmo]

Mixing client and server scripts together is not the common Meteor behavior.

I can workaround it, but it is not as fluent as desired.

Use case:
Winston is a pure server module. So create a small Winston on the client as well and pass the arguments down to the server is desired.

In this case the Winston stub gets overwritten by the client implementation, since unit directories are loaded by karma first.

[samhatoum]

Interesting idea. I've been thinking to run server unit tests using jasmine-node, and for browser tests to run in phantom/chrome to be more realistic.