Closed Bug 574709 Opened 14 years ago Closed 14 years ago

[mozmill] AssertJS failure in testGetMoreSearchEngines.js

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

Product:
Mozilla QA Graveyard
Component:
Mozmill Tests
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: aaronmt, Assigned: whimboo)

References

(
URL
)

Details

(Whiteboard: [mozmill-test-failure][fixed by bug 604832])

MODULE: firefox\testSearch\testGetMoreSearchEngines.js TEST: testGetMoreSearchEngines FAIL: Controller.assertJS("subject.URLContainsText == true") BRANCH: 1.9.1 http://brasstacks.mozilla.com/couchdb/mozmill/_design/reports/_show/report/e58ed9da807511df9365005056a533eb Currently, I am only seeing this as an issue on 1.9.1 and on Linux as per the aforementioned test result.
It appears as though this test is sometimes failing on Shiretoko when a search is conducted with nothing typed in the search box
Could this be another test which suffers from the focus issues we have with Shiretoko?
(In reply to comment #2) > Could this be another test which suffers from the focus issues we have with > Shiretoko? Don't believe it's a focus issue as I have the browser window in focused during the test run. This is only happening when a download of a new search engine takes place.
We should update the test to use a local test case. There is a preference we can use so clicking on the more engines button will open a localhost page. See the constants at the top of the SearchAPI.
The reason why it is broken is the same as bug 575241. With the change to local test data we can leave that issue alone.
(In reply to comment #5) > The reason why it is broken is the same as bug 575241. With the change to local > test data we can leave that issue alone. I don't believe this is the same issue as the failure reported in this bug is after the search engine is installed and selected.
Well, as what I was able to see on qa-horus today was, that we show the xml file instead of installing the search engine. I have no idea if that's always the case. Just to let you know about.
Hmm could be, we'll wait
No needs to wait for. With the move to a local test case we will not suffer from it anymore.
Assignee: aaron.train → hskupin
Component: Search → Mozmill Tests
Depends on: 604832
Product: Firefox → Testing
QA Contact: search → mozmilltests
Whiteboard: [mozmill-test-failure] → [mozmill-test-failure][will be fixed by bug 604832]
Version: 3.5 Branch → unspecified
Looks to be fixed by bug 604832.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [mozmill-test-failure][will be fixed by bug 604832] → [mozmill-test-failure][fixed by bug 604832]
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
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.