Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

cabal-validate: "Keep going" mode #10572

Open
9999years opened this issue Nov 20, 2024 · 0 comments
Open

cabal-validate: "Keep going" mode #10572

9999years opened this issue Nov 20, 2024 · 0 comments
Labels
cabal-validate validate.sh (cabal-validate) test suite runner meta: tracking re: devx Improving the cabal developer experience (internal issue) type: testing Issues about project test suites

Comments

@9999years
Copy link
Collaborator

If any tests fail, the whole ./validate.sh script exits early. This is useful for quick feedback, but can make it annoying to get a grasp on the full set of errors when making larger refactors. I have to fix all the errors in a test suite before I can get to the next one to even see if it errors.

Proposal: There should be a --keep-going or --no-fail-fast option which continues even if a test suite fails. The exit code should still be set the same (any test failures lead to a non-zero exit code) and a summary of which steps passed or failed should be printed at the end of the output.

@9999years 9999years added meta: tracking re: devx Improving the cabal developer experience (internal issue) type: testing Issues about project test suites cabal-validate validate.sh (cabal-validate) test suite runner labels Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cabal-validate validate.sh (cabal-validate) test suite runner meta: tracking re: devx Improving the cabal developer experience (internal issue) type: testing Issues about project test suites
Projects
None yet
Development

No branches or pull requests

1 participant