Closed Bug 468914 Opened 11 years ago Closed 11 years ago

Run reftest twice: first with the tests that assert and make assertions non-fatal, next with the set that don't assert and make assertions fatal

Categories

(Testing :: Reftest, defect, major)

Product:
Testing
Component:
Reftest
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: Waldo, Unassigned)

References

Details

(Keywords: autotest-issue) 

If we annotate the tests that cause assertions in the reftest manifests, it's a simple modification to make reftest only run those tests (or their complement).  With that modification and the ability to control environment variables when a reftest run occurs (bug 468913 would make this possible), over time we can get to a point where we can make assertions fatal in all reftests.  I think this would be the easiest path to testing for assertions without having to be too worried about regressions undoing all previous work at assertion-free behavior (while still making it easy to switch a test from a run that tolerates assertions to one that doesn't).
Wontfix in favor of bug 472557?
Yes.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.