This repository has been archived on 2020-01-20. You can view files and clone it, but cannot push or open issues or pull requests.
node-spearhead/test
2015-12-30 16:12:17 -08:00
..
integration joyent/node-triton#67 triton create should support assigning tags 2015-12-30 16:12:17 -08:00
lib Integration test config handling improvements. Add 'ResourceNotFound' error and fine tune exit status handling. 2015-10-06 23:24:42 -07:00
unit joyent/node-triton#67 triton create should support assigning tags 2015-12-30 16:12:17 -08:00
config.json.sample joyent/node-triton#39 change the test config 'destructiveAllowed' var to 'writeActionsAllowed' 2015-10-07 12:19:26 -07:00
README.md a start at a test framework 2015-09-01 00:31:00 -07:00
runtests a start at a test framework 2015-09-01 00:31:00 -07:00

The node-triton test suite.

There are two sets of tests here: unit tests which can be run in your local clone (see "test/unit/") and integration tests which are run against a cloudapi.

WARNING: While this test suite should strive to not be destructive to existing data in the used account, one should take pause before blindly running it with one's cloudapi creds.

Usage

Unit tests should be run before commits:

make test

Or you can run a specific test file via:

cd test
./runtest unit/foo.test.js

Integration tests: XXX how to run?

Development Guidelines

  • We are using tape.

  • Use "test/lib/*.js" and "test/{unit,integration}/helpers.js" to help make ".test.js" code more expressive:

  • Unit tests (i.e. not requiring the cloudapi endpoint) in "unit/*.test.js". Integration tests "integration/*.test.js".