Console test runner does not return non-zero exit code when there are invalid tests
Bug #997871 reported by
Ergwun
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| NUnit V2 |
Fix Released
|
Medium
|
Charlie Poole | ||
Bug Description
If a test fixture constructor throws an exception, the tests in that fixture are categorised as invalid, and the GUI runner will turn the progress bar red, but the console runner does not return a non-zero error code (at least in v 2.5.5).
Returning a non-zero error code would allow build scripts (e.g. MSBuild) to automatically treat this as a failure.
As discussed here: https:/
Related branches
| Changed in nunitv2: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in nunitv2: | |
| assignee: | nobody → Charlie Poole (charlie.poole) |
| milestone: | none → 2.6.1 |
| Changed in nunitv2: | |
| status: | Triaged → Fix Committed |
| tags: |
added: console removed: console-test-runner |
| Changed in nunitv2: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
