npm posttest does not work when tests fail in npm test

[nirvanagit]

npm test has a pre and a post.
On passing test. npm test triggers npm posttest.

But when any of the test cases fail, npm test does not trigger posttest.

@isaacs - You are the best person for this.

[smikes]

Is this still a problem for you?

I believe this is unlikely to change, since the contract on the pre/thing/post scripts is implicitly npm run-script prefoo && npm run-script foo && npm run-script postfoo -- that is, the expectation is that the pre script can prevent later scripts from running, and that the post script will not run if the thing script failed.

Can you tell me a bit more about what you are trying to accomplish in posttest?

We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and re-open it!)

Thanks!

[othiym23]

In the vast majority of cases, users are going to be unpleasantly surprised if posttest runs after test failures (you don't want your test environment being cleaned up or new versions being published if there were test failures, for instance). As such, this behavior isn't going to change. Putting something like "test":"npm run-script test-failing || npm run-script mandatory-cleanup" into your package.json will give you what you want.

Closing as resolved!

[EdmondChuiHW]

Not reopening this issue, but just in case anyone find it helpful, I used npm-run-all for cross-platform capatibility, since || means different things in Windows vs Mac

"the-actual-test": "…",
"test": "npm-run-all the-actual-test run-after-test-even-if-failed --continue-on-error",
"run-after-test-even-if-failed": "…"