The default bug view has changed. See this FAQ.

Mozmill test failure testSearch/testAddMozSearchProvider | Current URL contains the wrong search term

RESOLVED FIXED

Status

Mozilla QA
Mozmill Tests
RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: vladmaniac, Assigned: vladmaniac)

Tracking

unspecified

Firefox Tracking Flags

(firefox14 fixed, firefox15 fixed, firefox16 fixed, firefox17 fixed, firefox-esr10 fixed)

Details

(Whiteboard: [mozmill-test-failure][functional], URL)

Attachments

(1 attachment, 3 obsolete attachments)

(Assignee)

Description

5 years ago
This is failing constantly on all platforms since MDN change lately and this test uses a search engine which points to a MDN search 

https://developer.mozilla.org/en-US/

Local error log: 
"message": "Current URL contains the search term - got 'https://developer.mozilla.org/en-us/users/login?next=/en-us/docs/new%3fslug%3dspecial%253asearch', expected 'firefox'"
matches mozmill-ci report: 

http://mozmill-ci.blargon7.com/#/functional/report/29fc09ba0c8360d637617903a01a793b

Mozmill version: 1.5.17
Platforms: all
(Assignee)

Updated

5 years ago
Whiteboard: [mozmill-test-failure][functional]
(Assignee)

Updated

5 years ago
Assignee: nobody → vlad.mozbugs
Status: NEW → ASSIGNED
(Assignee)

Comment 1

5 years ago
Created attachment 649192 [details] [diff] [review]
quickey v1.0

So this is a simple fix - 
* just changed the search term because there were no search results in the new MDN for "Firefox" string.
* also, in the long term, I would suggest switching MDN with a mozqa page - not a local search engine (because this is the only test remaining to use the modal dialog and thoroughly test the UI and IMO we need it). MDN points to a browser ID login at the moment and I don't think we want to use credentials in our tests (I mean we did not so far)
Attachment #649192 - Flags: review?(dave.hunt)
(Assignee)

Updated

5 years ago
status-firefox-esr10: --- → affected
status-firefox14: --- → affected
status-firefox15: --- → affected
status-firefox16: --- → affected
status-firefox17: --- → affected
(Assignee)

Comment 2

5 years ago
The patch will apply cleanly also on mozilla-esr10 branch
(Assignee)

Updated

5 years ago
Attachment #649192 - Flags: review?(hskupin)
Comment on attachment 649192 [details] [diff] [review]
quickey v1.0

>-  searchBar.search({text: "Firefox", action: "goButton"});
>+  searchBar.search({text: "Mozilla", action: "goButton"});

This is not a valid change. The string 'mozilla' appears in the URL because of the domain name, not because the search term has been passed correctly. This makes the test a false positive as the search functionality is not being tested at all.

We should change this test to use a local page, or at least to use mozqa.com.
Attachment #649192 - Flags: review?(hskupin)
Attachment #649192 - Flags: review?(dave.hunt)
Attachment #649192 - Flags: review-
(Assignee)

Comment 4

5 years ago
Created attachment 649217 [details] [diff] [review]
fix patch 2.0

Fixed to use a page from mozqa.com 
Thanks Dave for the fast review
Attachment #649192 - Attachment is obsolete: true
Attachment #649217 - Flags: review?(dave.hunt)
(Assignee)

Updated

5 years ago
Attachment #649217 - Flags: review?(hskupin)
Comment on attachment 649217 [details] [diff] [review]
fix patch 2.0

If we are going to use mozqa.com we have to update the whole XML file. Just replacing the Url entry is not all as you can see when closely watching the file.

Also, I still want to see this test using a local search provider, but that's clearly a different bug.
Attachment #649217 - Flags: review?(hskupin)
Attachment #649217 - Flags: review?(dave.hunt)
Attachment #649217 - Flags: review-
(Assignee)

Comment 6

5 years ago
Created attachment 649220 [details] [diff] [review]
patch v2.1

You're right, sorry for missing the rest of the details.
Attachment #649217 - Attachment is obsolete: true
Attachment #649220 - Flags: review?(hskupin)
(Assignee)

Updated

5 years ago
Attachment #649220 - Flags: review?(dave.hunt)
Comment on attachment 649220 [details] [diff] [review]
patch v2.1

>+  <ShortName>Moz Search</ShortName>

Please use 'mozqa.com' as short name.

>+  <Description>Mozilla QA Search Results Page</Description>

Same here: 'Mozqa.com search results'
Attachment #649220 - Flags: review?(hskupin)
Attachment #649220 - Flags: review?(dave.hunt)
Attachment #649220 - Flags: review-
(Assignee)

Comment 8

5 years ago
Created attachment 649248 [details] [diff] [review]
patch v2.2

fixed
Attachment #649220 - Attachment is obsolete: true
Attachment #649248 - Flags: review?(hskupin)
(Assignee)

Updated

5 years ago
Attachment #649248 - Flags: review?(dave.hunt)
Comment on attachment 649248 [details] [diff] [review]
patch v2.2

I will land it across branches now. Vlad, please file an infrastructure bug so we can get the XML file updated in the litmus-data repository.
Attachment #649248 - Flags: review?(hskupin)
Attachment #649248 - Flags: review?(dave.hunt)
Attachment #649248 - Flags: review+
http://hg.mozilla.org/qa/mozmill-tests/rev/c9cc7d5a8269 (default)
http://hg.mozilla.org/qa/mozmill-tests/rev/1227f70eb535 (aurora)
http://hg.mozilla.org/qa/mozmill-tests/rev/ec753932eb96 (beta)
http://hg.mozilla.org/qa/mozmill-tests/rev/9c64d7f8ff0f (release)
http://hg.mozilla.org/qa/mozmill-tests/rev/29843ea9d97b (esr10)
Status: ASSIGNED → RESOLVED
Last Resolved: 5 years ago
status-firefox-esr10: affected → fixed
status-firefox14: affected → fixed
status-firefox15: affected → fixed
status-firefox16: affected → fixed
status-firefox17: affected → fixed
Resolution: --- → FIXED
Blocks: 780619
You need to log in before you can comment on or make changes to this bug.