- Add meteor-mocha wrapper script to npm bin scripts
- Add meteor-mocha wrapper script
-
Add spacejam-mocha
-
Document mocha support in package desc, readme and help
-
Let mocha report uncaught client side exceptions during tests, instead of exiting.
- Add set-meteor-env and unset-meteor-env to package.json bin so other scripts can find them.
-
Add multi-env support to mrun and sjtp scripts using set-meteor-env and unset-meteor-env scripts
-
Add spacejam.rc script that adds the following aliases to the user's shell
menv XXX (i.e. menv STAGE) - switches between envs
msetenv - regenerates the meteor env
-
Add spacejam-init-bashrc script that adds to user's .bashrc the menv and msetenv aliases by sourcing spacejam.rc
-
Add mdeploy script to login and publish an app to meteor, with multi-env support
-
Add mongo-connect and mongo-reset scripts to reset an external mongodb
-
Add mmpublish script to publish packages with practicalmeteor:mocha tests
-
TODO: Documentation of all of the above in README
- Exit with exit code 6 in case of an uncaught client side error before or during tests.
-
Add support for METEOR_APP_HOME in mrun
-
Always export METEOR_TEST_PACKAGES='1' in both spacejam and mtp before running meteor test-packages
- Add --use-system-phantomjs flag.
- Add support for saving xunit output generated by meteor's test-in-console to a file using --xunit-out
- Add --phantomjs-options
- Remove requirement to be in a meteor app or package folder
- Mac / OS X support
- Update README.md
- coffee-script installation perquisite removed.
- Add --dir option to specify current working directory.
- Unless you explicitly specify --mongo-url, mongodb will default to internal meteor mongodb, and not MONGO_URL.
- Unless you explicitly specify --root-url, ROOT_URL will default to localost:--port (default 4096), and not ROOT_URL.
- Add mrun and mtp scripts
- Internal: Update tests to meteor 1.0
- Internal: Compile and run tests in js, not coffee.
- Remove support for the --app option. spacejam needs to be run from within a meteor app or package folder.
- Remove support for the --once option, since we need the meteor proxy to start and launch a mongodb, if needed. With --once, the meteor proxy will not launch a mongodb.
- Remove support for the --driver-package option. It will always be test-in-console, since spacejam should only be used to test your packages from the command line or in ci environments.
- Internal: Update tests to meteor 0.9.2.2
- Internal: Fix npm-publish script so it stops in case of errors.
- Add support for running spacejam without packages specified, so it will do the same as meteor test-packages without arguments.
- Add support for running tests for standalone packages, without a meteor app.
- spacejam now kills meteor's internal mongodb cleanly. See #3
- Updated documentation to reflect that spacejam_ environment variables need to be lower case.
--driver-package
option has been removed. It will always usetest-in-console
.- Updated documentation to include prerequisites (coffee-script) and quick start.
--app
is no longer required. spacejam will use the current working directory, if no --app folder is specified.- Added spacejam (bin/run-tests.sh) and meteor (bin/run-app.sh) wrapper scripts in order to easily specify different environments for meteor and spacejam.
- Added a script (bin/unset-meteor-env.sh) to easily unset meteor related environment variables.
- Add support for the
--release
meteor flag.