-
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
Report bad test() usage as a test failure, rather than a runtime error #698
Comments
I like the idea of being as graceful a possible. One concern though. Look at it the other way around. What if you have a lot of tests and you use one of them incorrectly. Now it will run all the tests before letting you know you have an issue and then you'll have to rerun the whole test file again. Just a thought. |
#78 will likely force our hand here. We're doing #696 so we can correctly run exclusive test but I doubt we'll try and suss out these issues statically. If we don't then we'll end up in situations where we're already running a whole bunch of tests before the fault is encountered. Then why not run to completion? |
No reason we can't report it as an error as soon as it's encountered. |
You probably won't notice it though. |
Why not? If it increases the error count, that's noticeable immediately. |
Fair enough. |
This will be easiest to implement once #2217 lands. |
@IssueHunt has funded $40.00 to this issue.
|
Sometimes you get sloppy / distracted and end up with a half completed test:
Instead of throwing when someone misuses the API, I think the misuse should just be reported as a failure. It should still execute the correctly written tests.
The text was updated successfully, but these errors were encountered: