test errors should be reported differently from test failures

Bug #1214063 reported by Nate Finch
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gocheck
New
Undecided
Unassigned

Bug Description

Right now there's very little visual different between a test failure (result == false) and a test error (error != ""). The only difference I see is an additional line of text that indicates the error, which is not significantly different from the lines simply showing the values passed into the check.

Test errors indicate a problem with the test, whereas test failures indicate a problem with tested function (at least, that appears to be the intent). It would be useful if test errors were counted separately from failures, and given an indicator that's different than simple failure, so it's clear to the test writer that the test needs to be fixed, not the tested function.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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