Test failure 'this.controller.browserObject.browsers[index] is undefined' in /testSecurity/testSafeBrowsingNotificationBar.js

RESOLVED WONTFIX

Status

P4
normal
RESOLVED WONTFIX
4 years ago
4 years ago

People

(Reporter: danisielm, Unassigned, Mentored)

Tracking

unspecified

Firefox Tracking Flags

(firefox32 wontfix, firefox33 affected, firefox34 affected, firefox35 affected, firefox36 affected, firefox-esr31 affected)

Details

(Whiteboard: [mozmill-test-failure][lang=js], URL)

(Reporter)

Description

4 years ago
Module:    remote
Test:      /testSecurity/testSafeBrowsingNotificationBar.js   
Failure:   this.controller.browserObject.browsers[index] is undefined
Branches:  Firefox Beta
Platforms: Windows XP

Only 1 failure, but let's keep track of this failure.
The problem here is that we do NOT wait for the new tab to being opened:

  button.waitThenClick();
  controller.waitForPageLoad(controller.tabs.getTab(1));

Lets make sure we use the tabbrowser class to open that new tab via a callback. This most likely happens on slow machines, and can appear at any time.
status-firefox32: --- → affected
status-firefox34: --- → affected
status-firefox35: --- → affected
status-firefox-esr31: --- → affected

Comment 2

4 years ago
Seems to fail rarely:
http://mozmill-release.blargon7.com/#/remote/report/447e3274a76247e6567e1c2aa6460a2f
status-firefox32: affected → wontfix
status-firefox36: --- → affected
OS: Windows XP → All
The possible solution to get this bug fixed has been mentioned in comment 1. So I think that makes it a good first and mentored bug.

More details in how to setup a working environment locally you can find here:
https://developer.mozilla.org/en-US/docs/Mozmill_Tests
Mentor: andrei.eftimie
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][lang=js][good first bug]

Comment 4

4 years ago
Hi, I would like to work on this bug. I am new to this and would greatly appreciate some guidance. I will look into comment 1 as mentioned by Henrik.
wrahman, that's great to hear. Even we are in a transition of those tests to another framework, a fix here would be helpful for other kind of builds for Firefox beside Nightly. So let me know if you have questions. For now please have a look at the updated URL in how to get the Mozmill tests running.
Assignee: nobody → wrahman0
Mentor: andrei → hskupin
Status: NEW → ASSIGNED

Comment 6

4 years ago
Thank you Henrik, I will keep you posted on the progress.

Comment 7

4 years ago
I have been busy looking into another bug. Hence, the late reply. Anyway, I have just realized that I only have mozilla-central checked out. I dont think I will get around to setting this env up this week. If in the meantime anyone wants to take this bug, feel free to.
We are going to close out the security tests for Mozmill soon given that we convert them all to Python. So I don't think it is useful anymore to invest more time on that bug, especially that it has already been converted.

Let me know if you want to work on something else instead.
Assignee: wrahman0 → nobody
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WONTFIX
Whiteboard: [mozmill-test-failure][lang=js][good first bug] → [mozmill-test-failure][lang=js]
You need to log in before you can comment on or make changes to this bug.