Closed
Bug 909229
Opened 12 years ago
Closed 12 years ago
[he] Test failure "'Main feature' element has been found - got 'false'" in /testSecurity/testSafeBrowsingWarningPages.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(firefox23 fixed, firefox24 fixed, firefox25 fixed, firefox26 fixed, firefox-esr17 fixed)
People
(Reporter: andrei, Assigned: AndreeaMatei)
References
()
Details
(Whiteboard: [mozmill-test-failure][reproducible])
Module: testWarningPages
Test: /testSecurity/testSafeBrowsingWarningPages.js
Failure: 'Main feature' element has been found - got 'false'
Branches: default
Platforms: all
Reproducible.
Reporter | ||
Comment 1•12 years ago
|
||
Reporter | ||
Updated•12 years ago
|
status-firefox26:
--- → affected
Comment 2•12 years ago
|
||
Why all platforms and a P1? I can only see a single failure in our dashboard.
Reporter | ||
Comment 3•12 years ago
|
||
100% reproduce rate.
We have only 1 failure in the dashboard because we only ran this locale once.
I've set it to P1 in lieu of the recent [localized] failures we've had that are 100% reproductible, but only affect a specific locale. ex: bug 905960
Comment 4•12 years ago
|
||
Ah ok. Thanks for the clarification.
![]() |
Assignee | |
Comment 5•12 years ago
|
||
We're failing here because the page we're loading after clicking the "Ignore this warning" button does not have the "main-feature" id on it:
This is the page:
http://www.mozilla.org/he/firefox/its-a-trap.html
Would this issue be valid to file a bug in Localization and have this id added?
I've created a testcase to check the element against each correspondent locale url and this is the only one failing.
Assignee: nobody → andreea.matei
status-firefox23:
--- → affected
status-firefox25:
--- → affected
status-firefox-esr17:
--- → affected
![]() |
Assignee | |
Updated•12 years ago
|
Status: NEW → ASSIGNED
![]() |
Assignee | |
Comment 6•12 years ago
|
||
This has been fixed by adding the id in the html page provided above, in bug 912936.
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•6 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
•