Skip to content

Commit

Permalink
chore: Remove test artefacts that ensure failure on subsequent tests (#…
Browse files Browse the repository at this point in the history
…1138)

If the tests fail with a bad 'test/fixtures/cli/foo-cache', then subsequent tests will also fail unless the cache is cleaned.
A failed test run also leaves a lot of files in 'test/temp-dir-nyc-integration' that are cleaned on success, but not before the start of the next run in case of failure.
  • Loading branch information
AndrewFinlay authored and coreyfarrell committed Jul 9, 2019
1 parent 4bc9c14 commit 421c5bd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion package.json
Expand Up @@ -9,7 +9,7 @@
"test": "tap -t360 --no-cov -b test/*.js",
"snap": "cross-env TAP_SNAPSHOT=1 npm test",
"posttest": "npm run report",
"clean": "rimraf ./.nyc_output ./node_modules/.cache ./.self_coverage ./test/fixtures/.nyc_output ./test/fixtures/node_modules/.cache ./self-coverage",
"clean": "rimraf ./.nyc_output ./node_modules/.cache ./.self_coverage ./test/fixtures/.nyc_output ./test/fixtures/node_modules/.cache ./test/fixtures/cli/foo-cache ./test/temp-dir-* ./self-coverage",
"instrument": "node ./build-self-coverage.js",
"report": "node ./bin/nyc report --temp-dir ./.self_coverage/ -r text -r lcov",
"release": "standard-version"
Expand Down

0 comments on commit 421c5bd

Please sign in to comment.