Closed
Bug 599502
Opened 14 years ago
Closed 13 years ago
Use of sleep() causes random failures/hangs in testMasterPassword
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
VERIFIED
WORKSFORME
People
(Reporter: u279076, Unassigned)
References
Details
(Whiteboard: [mozmill-test-failure])
File: firefox/restartTests/testMasterPassword/test1.js
// Get the Remember Password button based on the above label
var button = tabBrowser.getTabPanelElement(
tabBrowser.selectedIndex,
'/{"value":"password-save"}/{"label":"' + label + '"}'
);
UtilsAPI.assertElementVisible(controller, button, true);
controller.waitThenClick(button, TIMEOUT);
controller.sleep(500);
controller.assertNodeNotExist(button);
The above sleep causes a failure sometimes in the Master Password test. We should update the test to use a waitForEval instead.
Comment 1•14 years ago
|
||
Alongside the above, the code pasted shouldn't even work because we can't use getTabPanelElement for an expected notification box anymore because it's now changed to a doorhanger. This bug should depend on an API change
Comment 2•14 years ago
|
||
Please file a bug if there isn't one yet, so we can get the TabbedBrowsingAPI updated.
Comment 3•14 years ago
|
||
Move of Mozmill Test related project bugs to newly created components. You can
filter out those emails by using "Mozmill-Tests-to-MozillaQA" as criteria.
Product: Testing → Mozilla QA
What's left for this bug? Simply refactor it to stop using sleep()?
No longer blocks: 611455
Comment 5•13 years ago
|
||
I would leave it to you for now for investigation.
Comment 6•13 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #5)
> I would leave it to you for now for investigation.
I did not see any sleep call in this test. Perhaps we changed it in another bug and forgot to close this one?
Anyway, the code in Description does not appear to be in the test files. 1.9.2 branch?
There was no branch stated in the bug report so perhaps I am missing the branch
Comment 7•13 years ago
|
||
Yeah, i think that I have fixed that in another bug a long time ago. Can't remember which one. So closing as wfm.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•