Closed
Bug 620051
Opened 14 years ago
Closed 14 years ago
Timeout failure (waitForPageLoad) in testSafeBrowsingNotificationBar.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: aaronmt, Assigned: aaronmt)
References
()
Details
(Keywords: regression, Whiteboard: [mozmill-test-failure])
Attachments
(2 files)
1.82 KB,
patch
|
whimboo
:
feedback+
|
Details | Diff | Splinter Review |
1001 bytes,
patch
|
whimboo
:
review+
|
Details | Diff | Splinter Review |
MODULE: testSafeBrowsingNotificationBar.js TEST: testNotificationBar ERROR: controller.waitForPageLoad(): Timeout waiting for page loaded PLATFORM: All BRANCH: All Fixing this unmasked two problems in the test: a) goBack is untrustworthy, and b) another waitForPageLoad() issue resolved by acting on the activeTab rather than getTab.
Assignee | ||
Comment 1•14 years ago
|
||
Removed goBack() for open(), and used activeTab instead of getTab
Attachment #498472 -
Flags: review?(hskupin)
Comment 2•14 years ago
|
||
Comment on attachment 498472 [details] [diff] [review] Patch v1 - (default) >+++ b/firefox/testSecurity/testSafeBrowsingNotificationBar.js > // Go back to the notification bar >- controller.goBack(); >+ controller.open(badSites[i]); > controller.waitForPageLoad(); goBack() uses the bfcache which doesn't work with waitForPageLoad at the moment. See bug 605784. So removing it is the right approach here. >- controller.waitForPageLoad(controller.tabs.getTab(1)); >+ controller.waitForPageLoad(controller.tabs.activeTab); Why does getTab(1) fail? Do we have more than 2 tabs? Can you please give a more detailed explanation?
Attachment #498472 -
Flags: review?(hskupin) → feedback+
Assignee | ||
Comment 3•14 years ago
|
||
When I ran this it seemed to hang on getTab instead of activeTab, although, with some comparison testing now, I'm unable to see the behaviour again at home. I just did a couple runs cross platform and it's not needed. For refactoring, since the tab opened becomes the activeTab, I think it would make sense to change it in the future. Patch for review just has the switch from from goBack() to open()
Attachment #498738 -
Flags: review?(hskupin)
Updated•14 years ago
|
Attachment #498738 -
Flags: review?(hskupin) → review+
Comment 4•14 years ago
|
||
(In reply to comment #3) > home. I just did a couple runs cross platform and it's not needed. For > refactoring, since the tab opened becomes the activeTab, I think it would make > sense to change it in the future. Agreed on. In the same step we should check if we can apply that change also to other existent tests. Just for consistency.
Assignee | ||
Comment 5•14 years ago
|
||
default - http://hg.mozilla.org/qa/mozmill-tests/rev/ef576d0eb075 1.9.2 - http://hg.mozilla.org/qa/mozmill-tests/rev/93eb9734927f 1.9.1 - http://hg.mozilla.org/qa/mozmill-tests/rev/d18792253ec5
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
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
•