I’ve always written my meteor methods tests on neither client nor server, which means they run on both. I sometimes encounter frustrating errors when they run on the client, and am left wondering what the real benefit of it all is. It feels like I spend a lot of time stubbing and mocking packages and environments to make it work, when there might actually be no advantage of doing it.
I saw that MDG moved its method tests to be server only in their Todo’s repo:
So I’m wondering what the best practice is, am I detecting additional errors in my methods by running the tests on the client as well?