untested

Orders tests for a source code change based on code coverage analysis.

Scenario:

foo.js
bar.js // uses foo.js

tests/
    fooTest.js
    barTest.js

You have edited foo.js and rerun tests/fooTest.js. Are you done? No. Do you know which tests are somehow affected by foo.js? What if you have 100s of JavaScript source files and 100s of unit tests. Testing everything on every commit would take hours ...

untested is the solution.

1. Run a unit test using gt or lasso-node or solid-code, and you get code coverage results.
2. Throw these results into untested.
3. On a commit give the changelist to untested and get back ordered list of tests affected.
4. Run these tests first. Get the results right away.

License

MIT style license, see file.

Author

Contact Gleb Bahmutov [email protected] with any questions, etc.