Archived

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.

History

Trent Mick c0ad6bb378 joyent/node-triton#219 test: Fix test suite to not use non-existant `triton img rm -w` wait option		2017-07-31 16:31:19 -07:00
..
integration	joyent/node-triton#219 test: Fix test suite to not use non-existant `triton img rm -w` wait option	2017-07-31 16:31:19 -07: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#173 Add support for listing and getting triton nfs volumes	2017-07-20 23:48:27 +00:00
config.json.sample	joyent/node-triton#218 add 'allowVolumesTests' to test config and skip volumes tests by default	2017-07-28 16:57:55 -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

README.md

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".