Closed Bug 744279 Opened 12 years ago Closed 11 years ago

To detect [false] (random) timeouts is good, to warn about succeeding but too long tests would be even better

Categories

(Testing :: Mochitest, enhancement)

Product:
Testing
Component:
Mochitest
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: sgautherie, Unassigned)

References

(Blocks 1 open bug,
URL
)

Details

That feature would warn about random timeouts like bug 736325.

***

{
79 TestRunner.timeout = 5 * 60 * 1000; // 5 minutes.

438         TestRunner.log("TEST-END | " +
439                        TestRunner.currentTestURL +
440                        " | finished in " + runtime + "ms");
}

Add a (conditional) check that 'runtime' is not too close (5-10%?) to 'TestRunner.timeout'.
Should at least be a todo() (while fixing affected tests), probably an ok() (later).

Ted, do you agree?
Ted, what do you think of this? Should it get duped to the bug to move things to mozbase?
Flags: needinfo?(ted)
Whiteboard: [good first bug][lang=js]
I don't really understand what this bug wants.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(ted)
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.