-
Notifications
You must be signed in to change notification settings - Fork 84
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
Interpret the "0 test" situation as a failure #211
Comments
Recommendation on Slack, by @lread : @onetom, I would prefer a non zero exit in this scenario as well. But... it is also pretty easy to write a kaocha hook to achieve this. |
Thanks for suggesting this improvement! I think this makes a lot of sense. Maybe not as default behavior, but as an option you can enable. |
This could be a good candidate for #183 , we can already introduce a flag to opt-in, then change the default for |
Along similar lines, the Lines 104 to 106 in 3d83494
That might also make internal bugs like #208 more apparent. |
It seems that it can be related the PR #404 |
Currently tests pass and no fails are thrown when there are 0 tests.
Not sure if this kind of kaocha configuration is possible in the
tests.edn
, but it would be useful to have the kaocha fail when 0 tests are detected. This would help indicate that configurations are incorrect, similar to how an error is thrown, if a deftest doesn't contain any assertions. This will ensure that any mis-configurations can be brought to attentionThe text was updated successfully, but these errors were encountered: