Closed
Bug 554393
Opened 15 years ago
Closed 14 years ago
[mozmill] Fix broken test testBlueLarry.js
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Assigned: u279076)
References
()
Details
(Whiteboard: [mozmill-test-failure])
Attachments
(1 file)
3.92 KB,
patch
|
whimboo
:
review+
|
Details | Diff | Splinter Review |
This failure looks strange. Sadly we do not have any error output for assertProperty.
Controller.assertProperty() failed
Anthony, can you look at this failure?
Reporter | ||
Updated•15 years ago
|
Assigning to myself. Henrik, since you are the only person who runs these tests, is there a way to attach some sort of failure detail to all bugs? Even a screenshot of the failure would help; at least until we get an actual reporter up and running.
Assignee: nobody → anthony.s.hughes
Reporter | ||
Comment 2•15 years ago
|
||
I don't run it on my box. It's on the qa-mozill machine in the lab. The only output I have is the one given in the URL. How many assertProperty calls do we have?
Does this failure only occur on MacOSX? Are there similar failures for WinXP, Linux?
Reporter | ||
Comment 4•15 years ago
|
||
Sorry for not mentioning it before, but you can check for other results on that page: http://brasstacks.mozilla.com/couchdb/mozmill/_design/reports/_list/summary/summary
Just scroll down and check the reports with a test count > 180
Reporter | ||
Updated•15 years ago
|
Whiteboard: [mozmill-test-failure]
Reporter | ||
Comment 5•15 years ago
|
||
This is definitely a focus problem which occurs because of a failure in one of the already ran tests.
In bug 558404 I have added more output for the assertProperty method. We will try to get it into Mozmill 1.4.1. Means we will get better output next week.
Assigning to myself. I'll attempt to fix all security failures this quarter.
Assignee: nobody → anthony.s.hughes
Reporter | ||
Comment 7•14 years ago
|
||
The failure here is in:
Controller.assertProperty(ID: page-proxy-favicon) : https://bugzilla.mozilla.org/skins/custom/images/bugzilla.png ==
This fix is a minor change. Instead of using BMO, we now use WikiMO. Both sites are "blue" sites. However, BMO contains two favicons, creating problems with Mozmill; WikiMO only contains one favicon. This is a separate issue and will be addressed in a separate bug.
Attachment #446604 -
Flags: review?(hskupin)
Reporter | ||
Comment 9•14 years ago
|
||
Comment on attachment 446604 [details] [diff] [review]
Patch v1 (default)
>+ * The Initial Developer of the Original Code is Mozilla Foundation.
It's "the Mozilla Foundation". I will update it right before the checkin.
Otherwise it looks fine. r=me
Attachment #446604 -
Flags: review?(hskupin) → review+
Reporter | ||
Comment 10•14 years ago
|
||
Landed on all branches as:
http://hg.mozilla.org/qa/mozmill-tests/rev/623c6defaacf
http://hg.mozilla.org/qa/mozmill-tests/rev/14fc95cc90d9
http://hg.mozilla.org/qa/mozmill-tests/rev/329fc0a8bc6c
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 11•14 years ago
|
||
Mass 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.
Component: Security → Mozmill Tests
Product: Firefox → Mozilla QA
QA Contact: firefox → mozmill-tests
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
•