[Question] Why the restriction on client-side about mantra

[arunoda]

@sakulstra This is a good point.

I don't know if this counts for a lot of companies, but at least "we" did mainly server side testing till now and client-side was more like "monkeytesting(https://en.wikipedia.org/wiki/Monkey_test)" without automation.

This is the exact reason we are working on Mantra. To give a proper structure to your client side code. Once we do this, we'll touch the server side.
For the server side, our plan to use integration tests. (most probably we'll use gagarin)

[zimt28]

Once we do this, we'll touch the server side.

Nice! @arunoda, could you add a comment there, that you're not forgetting about the server-side? My app for now is mostly server side as well, so having a good architecture there is a must.

[arunoda]

@zimt28 This is the server side archi we suggest. https://kadirahq.github.io/mantra/#sec-Appendix-Server-Side-Directory-Layout

But I think Meteor Guide is planning for a much better one since they cover more stuff for the server side.
So, I think we can get some stuff from Meteor's integration testing approach.

If your app need more modularity on the server side, I suggest to follow the Meteor Guide approach on that. I think it's not out yet, but we can pre-access it.