testtools

TestCommand: please add the possibility of making test failures fatal

Bug #1132542 reported by Michał Górny
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
testtools
Triaged
Medium
Unassigned

Bug Description

Currently, the 'test' command just runs the test suite and relies on user reading the report. This is really inconvenient for automated testing.

For that reason, I'd like to ask you to add an option to make the test command actually fatal; that is, aborting setup.py with failure exit status. With that feature, it will be possible to run tests and automatically determine if they failed.

Revision history for this message
Jonathan Lange (jml) wrote :

Hi Michał,

I'm not 100% clear what you want here:

 1. `python setup.py test` to return with a non-zero exit code if the tests fail
 2. `python setup.py test` to optionally abort the test run immediately on the first failure
 3. Both 1 & 2

1. is a bug, 2. is a feature request.

Thanks,
jml

summary: - TestCommand: please add the possibility of making test failueres fatal
+ TestCommand: please add the possibility of making test failu\res fatal
summary: - TestCommand: please add the possibility of making test failu\res fatal
+ TestCommand: please add the possibility of making test failures fatal
Changed in testtools:
importance: Undecided → Medium
status: New → Incomplete
importance: Medium → Undecided
Revision history for this message
Michał Górny (mgorny) wrote :

I want `python setup.py test` to return with a non-zero exit code. Otherwise, I have to grep the output to know whether the tests succeeded which is fragile.

Jonathan Lange (jml)
Changed in testtools:
status: Incomplete → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.