verbose flag causes spurious test failures
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
zope.testing |
Won't Fix
|
Undecided
|
Unassigned | ||
zope.testrunner |
Invalid
|
Undecided
|
Unassigned |
Bug Description
The tests run fine on the trunk without any '-v' flag::
$ svn co $ZSVN/zope.
$ cd zope.testing
$ /opt/Python-
...
$ bin/buildout
...
$ bin/test --all
bin/test:16: DeprecationWarning: zope.testing.
/home/
from zope.testing.
Running zope.testing.
Set up zope.testing.
Ran 261 tests with 0 failures and 0 errors in 22.661 seconds.
Tearing down left over layers:
Tear down zope.testing.
but one fails when run with '-v'::
$ bin/test --all -v
bin/test:16: DeprecationWarning: zope.testing.
/home/
from zope.testing.
Running tests at all levels
Running zope.testing.
Set up zope.testing.
Running:
.....
Failure in test /home/tseaver/
Failed doctest test for doctest.txt
File "/home/
-----
File "/home/
Failed example:
doctest.
Expected:
(0, 1)
Got:
Trying:
x = 1 + 1
Expecting nothing
ok
1 items passed all tests:
1 tests in tmpquMzTs
1 tests in 1 items.
1 passed and 0 failed.
Test passed.
(0, 1)
.....
Ran 261 tests with 1 failures and 0 errors in 23.245 seconds.
Tearing down left over layers:
Tear down zope.testing.
Tests with failures:
/home/
This needs to be fixed in zope.testrunner, not zope.testing.