Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Support option to opt out of terminating on any failures #20

Open
crisptrutski opened this issue Dec 16, 2015 · 0 comments
Open

Support option to opt out of terminating on any failures #20

crisptrutski opened this issue Dec 16, 2015 · 0 comments

Comments

@crisptrutski
Copy link
Contributor

When chaining test runners together (eg. unit tests and in-browser scenario tests), it can be more illuminating to get all failures at once, not only those from the first runner to have failures.

It also seems useful to be able to hang onto the exit code until later - so that boot test test-cljs would still be able fail on CI given only boot-test failures.

Towards this end I'm considering an exit! task for boot-cljs-test, which hangs on to any prior failures. Crude, but perhaps workable with some amendments, can be seen in crisptrutski/boot-cljs-test#24

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant