Closed
Bug 604367
Opened 14 years ago
Closed 13 years ago
Restart tests should be able to jump to specific test modules
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: whimboo, Unassigned)
References
Details
(Whiteboard: [mozmill-1.5.2-][mozmill-2.0+])
There are situations when a specific test module from the restart test-run has to be executed multiple times. Right now we have to duplicate that file but are still limited to this hard-coded number of steps. We need more flexibility here so we can re-execute a test module given the results from within the currently run test module. We should even be able to jump to different states, i.e. test1.js -> test3.js -> test2.js.
As an example check our software update tests. A description can be found on bug 604364.
Reporter | ||
Comment 1•14 years ago
|
||
We not only want to repeat specific test modules but it should be possible to jump to a specific module back and forth. We really need this for our endurance tests which are planned to get implemented in the next weeks.
Summary: Restart tests should be able to repeat specific test modules → Restart tests should be able to jump to specific test modules
I think the hard work for this is done in my planned refactoring of jsbridge, so I think we get this done.
Whiteboard: [mozmill-1.5.2?] → [mozmill-1.5.2+]
Reporter | ||
Updated•14 years ago
|
Whiteboard: [mozmill-1.5.2-] → [mozmill-1.5.2-][mozmill-1.5.3?]
Updated•14 years ago
|
Whiteboard: [mozmill-1.5.2-][mozmill-1.5.3?] → [mozmill-1.5.2-][mozmill-1.5.3?][mozmill-2.0?]
The work to make this possible is the work in 584464. The actual bits to add the interface so that tests can then change their "next test" remain unknown as to whether we'll get to those for 2.0 or not. Tentatively, I'm leaning toward +'ing this, but want to wait to see the larger refactoring land first.
Depends on: 584464
Whiteboard: [mozmill-1.5.2-][mozmill-1.5.3?][mozmill-2.0?] → [mozmill-1.5.2-][mozmill-1.5.3?][mozmill-2.0+]
Reporter | ||
Comment 5•14 years ago
|
||
We can wait for 2.0. I don't think hotfix-1.5 is it worth spending time for.
Whiteboard: [mozmill-1.5.2-][mozmill-1.5.3?][mozmill-2.0+] → [mozmill-1.5.2-][mozmill-2.0+]
This is done because you now have the ability upon restart to declare the test you want to restart in. We will settle other issues with this when we port the update tests to 2.0.
The basics are here so marking WFM.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Comment 7•13 years ago
|
||
Follow-up bugs should be separately filed, or if this bug is reopened than actionable items should be clarified wrt the 2.0 (trunk) framework
Reporter | ||
Comment 8•13 years ago
|
||
Clint and Jeff, can you please specify details on how this can be done? Do we have example code in the Mutt test folder which exercises such a situation?
Blocks: 647268
Comment 9•13 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #8)
> Clint and Jeff, can you please specify details on how this can be done? Do
> we have example code in the Mutt test folder which exercises such a
> situation?
See comment 6, https://github.com/mozautomation/mozmill/blob/master/mozmill/README.md, and https://github.com/mozautomation/mozmill/blob/master/mutt/mutt/tests/js/test_runnershutdown.js
Assignee | ||
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•