Message226631
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:49 | michael.foord | set | recipients:
+ michael.foord, terry.reedy, rbcollins, ezio.melotti |
2014-09-09 09:03:49 | michael.foord | set | messageid: <1410253429.59.0.263153687318.issue18232@psf.upfronthosting.co.za> |
2014-09-09 09:03:49 | michael.foord | link | issue18232 messages |
2014-09-09 09:03:49 | michael.foord | create | |
|