This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author michael.foord
Recipients ezio.melotti, michael.foord, rbcollins, terry.reedy
Date 2014-09-09.09:03:49
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I'd agree that a test run that actually runs zero tests almost always indicates an error, and it would be better if this was made clear. 

I have this problem a great deal with Go, where the test tools are awful, and it's very easy to think you have a successful test run (PASS) when you actually ran zero tests.

Particularly with discovery you will want to know your invocation is wrong.

I'm agnostic on a new "--min-tests" parameter, but having zero tests found should return a non-zero exit code and display a warning.
Date User Action Args
2014-09-09 09:03:49michael.foordsetrecipients: + michael.foord, terry.reedy, rbcollins, ezio.melotti
2014-09-09 09:03:49michael.foordsetmessageid: <>
2014-09-09 09:03:49michael.foordlinkissue18232 messages
2014-09-09 09:03:49michael.foordcreate