-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
add --strict flag #1818
Comments
This may be a good solution to the problem of accidentally committing these. @mochajs/mocha any opinions? |
Hmm, I thought skipped tests are actually marked as pending? People do commit these (looking at you Not so sure about the tests marked as skipped/pending.. If I skip tests is because I don't want to run them anymore, not even in prod.. not sure about you. |
I would love to have this! If you do not want a test (even in prod): it's probably because this is a dead/outdated test and need to be deleted from the source code. |
cc @mochajs/mocha |
Could we use some different terminology so that it's not confused with node/v8's |
How about |
Stricter testing mode. Fails tests that are: pending, marked as skipped, marked as only, have duplicate title
What is the status of this issue? I've been following the related PRs but they seem to be all closed. I think this is an important configuration and I was surprised that it didn't exist since some commit could add a Thanks! |
I'd like a
--strict
CLI flag that will cause my tests to exit with non-zero status ifThe text was updated successfully, but these errors were encountered: