[alanning]

Initially Meteor didn't have any support for testing apps. Since it has always had support for testing packages, teams generally had to split their app up into several private packages to allow for testing (with benefits to modularity too).

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

[Touche]

> Initially Meteor didn't have any support for testing apps.

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?

[jimbobimbo]

The framework can make or break your testing. If it's very hard or impossible to mock parts of the framework, your testing will be significantly hindered.