Closed
Bug 572424
Opened 16 years ago
Closed 15 years ago
Allow restart tests to manipulate order of executed tests
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 604367
People
(Reporter: whimboo, Unassigned)
Details
In the current state we have situations where we need multiple restarts of the browser but we can't predict how many that will be. As example you can take the software update tests. Right now we are only able to apply one single update, but if we have situations like for 3.6.4 build 7 it can happen that multiple updates are in the queue. That said the tests should be able to tell Mozmill that a specific restart test should called again after the next restart. It's something like a state machine. We are able to do such things for normal tests but with restart tests we are really limited. It's a static order of tests which get executed.
We could use the persisted object and a specific member to control the command line side of Mozmill which test has to be executed next within a folder. Mozmill should jump to that test and execute successive tests as they appear in the normal order.
| Reporter | ||
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
| Reporter | ||
Updated•15 years ago
|
Whiteboard: [mozmill.next?]
| Assignee | ||
Updated•10 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•