apycot-moved #9061 bad python_unittest status [resolved]
if some tests are executed, and some other test files are discovered but no test are found inside them, final status should be 'error' whatever the status of executed tests. | |
priority | normal |
---|---|
type | bug |
done in | 1.8.0 |
load | 0.500 |
load left | 0.000 |
closed by | <not specified> |
similar entities
Comments
-
2010/01/27 10:04, written by pydavid
-
2010/01/27 10:19
-
2010/01/27 16:51, written by pydavid
-
2010/01/27 17:32, written by sthenault
-
2010/01/28 09:37, written by pydavid
-
2010/01/28 15:42, written by pydavid
add commentAt the moment we have the following priority:
Does this ticket mean you would prefer:
or even further:
IMO, We should follow xUnit definition. A recent discussion about that is available in the archive of testing-in-python list.
xunit introduce two new status xfail and xpass (expected fail and unexpected fail). We may introduce them but some of apycot status higher level and will continue to be distinct (for example the skipped status have a different semantic than xUnit skipped test)
pyves: start by specifying what each status means.
pyunit and pytest checker return a wrong status for empty file