-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve stryker execution time regarding test command #82
Comments
I filed stryker-mutator/stryker-js#2286 |
karfau
added a commit
to karfau/xmldom
that referenced
this issue
Jul 4, 2020
Tests for `test/assert.js` need to run before the vows testsuite, not as part of them. - Rename `test/assert.vows.js` to `test/assert.vows.checks.js` - Script `test:assert` only runs those tests - Script `test:assert:strict` runs them with strict assertions - Script `test:unit` and `test:vows` are currently the same (until we add another testing framework to the mix) In the end `npm [run] test` executes the same amount of tests on CI but it's more easy to run a subset. Added devDependency [`npm-run-all`](https://www.npmjs.com/package/npm-run-all) xmldom#82 xmldom#77 (comment)
brodybits
added a commit
that referenced
this issue
Aug 17, 2020
Tests for `test/assert.js` need to run before the vows test suite, not as part of them. - Rename `test/assert.vows.js` to `test/assert.vows.checks.js` - Script `test:assert` only runs those tests - Script `test:assert:strict` runs them with strict assertions - Script `test:unit` and `test:vows` are currently the same (until we add another testing framework to the mix) - Update script `test` to run strict assertions only on `test/assert.vows.checks.js` In the end `npm [run] test` executes the same amount of tests on CI but it's more easy to run a subset. Added devDependency [`npm-run-all`](https://www.npmjs.com/package/npm-run-all) #82 #77 (comment) Co-authored-by: Christian Bewernitz <coder@karfau.de> Co-authored-by: Chris Brody <chris.brody+brodybits@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
as discussed in #77 after merging
scripts
structure => test: Restructure & improve npm test scripts #87I will focus on these tasks before any other.
The text was updated successfully, but these errors were encountered: