Files
meteor/tools/tool-testing
David Glasser 2b6b02439d destroy universe
"universe" was an old attempt to allow you to run various MDG
servers (Meteor Developer Accounts, the package server, an old version
of the Galaxy deploy server, etc) on localhost and configure the tool to
talk to it not via a bunch of environment variables but via a file
called "universe" at the root of your checkout. Nobody uses this (and
most of the URLs have environment variables for them anyway).  Simplify
the code by removing this entirely.

Also remove some more dead code, and a test that claims it only runs if
you have universe set up.
2016-05-13 15:09:03 -07:00
..
2015-08-06 16:44:07 -07:00
2015-08-07 12:32:35 -07:00
2016-05-13 15:09:03 -07:00

Tools testing

Running end-to-end tests happens through the Self-Test. To run the tests:

./meteor self-test <regexp>

A very-very useful environment variable to set, in case you are running on a slow machine:

# set the multiplier for time-outs
set TIMEOUT_SCALE_FACTOR=3

Writing tests

All tests are currently stored at /tools/tests/, each JS file can register a self-test. Example:

selftest.define("mongo failover", [/* tags */], function () {
  var s = new Sandbox();
  s.set('METEOR_TEST_MULTIPLE_MONGOD_REPLSET', 't');
  s.createApp("failover-test", "failover-test");
  s.cd("failover-test");

  var run = s.run("--once", "--raw-logs");
  run.waitSecs(120);
  run.match("SUCCESS\n");
  run.expectEnd();
  run.expectExit(0);
});

The example above demonstrates how to define a test, create a Sandbox, create an app from a template and run the Meteor commands.

Templates for apps and packages are kept in /tools/tests, too.

Testing with Phantom/Browserstack

The sandbox has a testWithAllClients method that runs the clients like Phantom or Browserstack pointed to the page of the app (localhost:3000 by default).

Tags

Tags are arbitrary. To make tags do anything, you should edit the selftest.js code.

Examples of some tags that exist today:

  • slow - the test is skipped, unless the --slow flag is passed
  • windows - the test is not run unless on Windows
  • net - the test is talking to external Internet services, thus requires an Internet connection to run

There are others.

Self-test gotchas

  • The docs for self-test is reading the code of self-test
  • run.forbid(regexp) forbids the regexp from the entire output, not from the point it was called. It happens, because the output is matched asynchronously.