* Yaroslav Halchenko <deb...@onerussian.com>, 2012-04-23, 09:17:
The “failures” was caused by the following misfeature of the
specification: “if a test […] prints to stderr, it is considered to
have failed.” But nosetests does print stuff to stderr even if
everything is all right (see bug #460242).
yikes -- doesn't it fail if underlying "test command" returns with
non-0 exit code?
Thankfully it does. :)
s/[…]/exits nonzero, or/ - sorry for the confusion.
IMHO that should be the criterion, not catching stderr, which might
have some spurious output from tests which might be testing either
application handles erroneous cases correctly (where it might output to
stderr).
ACK. Even if nosetests printed the usual stuff to stdout, I would still
have to redirect stderr to stdout (or /dev/null), because the tested
code could rightfully emit warnings.
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120423143025.ga3...@jwilk.net
