:factory: Development test runner for webpack to improve TDD experience. Runs only specs affected by code change. Serve test files from memory. For large project with hundreds of test files.
33
stars
5
forks
source link
v0.4 — Cache coverage data for non-executed test files. Introducing adapters. #1
This release comes with better code coverage handling. More specifically, it will remember the test coverage of previously run tests. This mean you will always get a live coverage report as if all tests were run.
Help me test this out:
npm i --save-dev 'taskworld/test-bed#better-coverage-mocha'
To accomplish this, the test framework needs to tell test-bed when it starts executing a test file as well as when it finished. This means that the test-entry.js needs to be updated.
It’s probably not a good idea to have to update the test-entry.js every time a new feature (that needs integration with test framework) is added. Therefore, test-bed now ships with adapters for few test frameworks (only Mocha right now as we only use Mocha).
Please look at the new README.md on how to create the test-entry.js.
v0.4
This release comes with better code coverage handling. More specifically, it will remember the test coverage of previously run tests. This mean you will always get a live coverage report as if all tests were run.
Help me test this out:
To accomplish this, the test framework needs to tell test-bed when it starts executing a test file as well as when it finished. This means that the
test-entry.jsneeds to be updated.It’s probably not a good idea to have to update the
test-entry.jsevery time a new feature (that needs integration with test framework) is added. Therefore,test-bednow ships with adapters for few test frameworks (only Mocha right now as we only use Mocha).Please look at the new README.md on how to create the
test-entry.js.