-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Print a reminder when --fail-fast
is on
#1134
Comments
I agree we should make it clear, maybe instead by showing the number of pending tests that didn't run? |
That would be a welcome addition. |
I would like to give this a shot. I am not sure exactly how to go about it yet though, so any pointers are appreciated. Sindre, for your idea of showing pending tests got any idea how would that work? From what i have seen so far it looks like once a test fails with the --fail-fast flag enabled Ava collects the test results that have been generated so far then starts teardown. |
Hi @ThomasBem! The test process that encounters the error simply exits if I think it'd be reasonable to compute a I'm marking this as |
Thanks for the feedback. I'm still interested in seeing if i can figure this out and make a contribution :) |
I noticed #1158 while researching this. Whatever we do there, it's likely that we won't have determined the total test count by the time a failure occurs. Thus the error message should say something like "There are at least 5 tests remaining". There might be more, but we just don't know. |
"`--fail-fast` is on. Any number of tests may have been skipped" would be fine as a start, no? |
So i have implemented some code that should have the test reporter spit out what @mightyiam suggested.
I have added a few tests and things seem to be working alright. But is there a way for me to run the Ava code that i now have locally as a test-runner for a separate test project just to verify that everything works as intended all the way through? |
@ThomasBem to install AVA that's in the working directory, in whatever project, I would do Although this wouldn't replace decent tests in my mind. |
I have posted a PR that fixes this issue under #1160. Please let me know what you guys think :) |
|
When a run stops due to a fail and when
--fail-fast
was provided, I'd like there to be a bold notice somewhere, perhaps at the bottom of the output, reminding me that--fail-fast
is on, so that I will never mistakenly think that I have only one failing test.The text was updated successfully, but these errors were encountered: