Orders tests for a source code change based on code coverage analysis.
foo.js bar.js // uses foo.js tests/ fooTest.js // tests foo.js barTest.js // tests bar.js
untested is the solution.
- Run a unit test using gt or lasso-node or solid-code, and you get code coverage results.
- Throw these results into untested.
- On a commit give the changelist to untested and get back ordered list of tests affected.
- Run these tests first. Get the results right away.
npm install -g untested
From examples/basic folder
gt fooTest.js // add test point info to untested gt barTest.js // add test point info to untested untested --affected foo.js // returns both fooTest.js and barTest.js
From examples/html folder
lasso-node index.html // add test point info to untested untested --affected foo.js // returns index.html
If you are using git, you can ask untested to run unit tests for all modified files (files returned by git diff --name-only).
untested --git // returns list of unit tests for all modified files untested --git --run // runs unit tests for modified files using gt or lasso-node
MIT style license, see file.
Contact Gleb Bahmutov email@example.com with any questions, etc.