Aesthetically, the app looks great. Is it normal for there to be zero test coverage in a meteor app? That concerns me. I did see this thread in the issue tracker: https://github.com/wekan/wekan/issues/467
The Velocity project [1] was started to address this issue and now supports testing apps with Jasmine, Cucumber, and Mocha. There are also individual testing frameworks for Meteor apps such as Nightwatch (now StarryNight).
Even with Velocity, testing a Meteor app is not as easy to set up as testing a Rails app so I would guess most teams don't make it a priority unless they are going into production.
Packages, however, are another story and my impression is that all of the most popular packages [2] have fairly extensive test suites.
1. http://velocity.meteor.com 2. https://atmospherejs.com/packages/most-used
I don't understand what this means... why do you need a framework to "support" testing. Can't you just... write a test using QUnit or Mocha or Tape or whatever you like?
In my experience, yes. Meteor has traditionally had a culture that focused a lot on tech demos and experimental projects, rather than stability and production. Sort of the anti-Angular 1.x. :)
(Man, I wonder if that comparison will annoy Angular fans or Meteor fans more? But I think it has some truth in it.)