CircleCI doc states that:
all test commands are run to completion, but a non-zero exit code during setup will cause the build to fail early.
Adding a new option to “fail early” during test just like during setup would be great, so that the build execution would be faster and test commands following a failed one would not be executed.
My use case for the second point is this:
- the latest test command of my circleci triggers a new parametrized build using the API. This new build runs additional and longer test cases.
- I don’t want to trigger this additional build if any of the previous faster tests have failed: I’d prefer the build to be stopped and be marked as failed.