Not passing should not always exit with code 1

Question

Not passing should not always exit with code 1

Closed this issue 8 years ago · 3 comments

If you write all your tests ahead of time, you might not want to fail your tests when not everything works, this will clog up a build server that simply needs to generate a report and a progress build of the app. We need a progressBuild cli flag to not fail on test failure

Answer 1 · 2016-12-13T13:25:16.000Z

Not sure if I understand it well. Can you provide an example?

Answer 2 · 2017-01-12T21:58:35.000Z

Closed due discontinued conversation.

Answer 3 · 2017-01-12T22:37:07.000Z

In other words this should work more like coverage reports with an option to fail on any non-passing test OR generate a report and exit with exit code 0. Otherwise when run on a CI server all tests must always pass