Closed
Bug 543685
Opened 15 years ago
Closed 15 years ago
Exclude robots from scanning test results on Brasstacks [@ testLocationBarSearches.js]
Categories
(Testing Graveyard :: Mozmill, defect)
Testing Graveyard
Mozmill
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [mozmill-test-failure])
We have a recent regression in one of our Mozmill tests which report to brasstack:
could not validate element XPath: /html/body[@id='gsr']/div[@id='cnt']/div[@id='res']/div/p[1]/b with text oau45rtdgsh34nfr
That test is running a feeling lucky search against Google and doesn't expect to get back a search result. But Google already knows about this search term because it scans all our test results:
http://www.google.de/search?hl=en&source=hp&q=oau45rtdgsh34nfr&btnG=Google+Search&aq=f&oq=
I feel that we should exclude search robots from scanning our Mozmill results on brasstacks.
Clint, can we do that?
Assignee | ||
Comment 1•15 years ago
|
||
I have added a meta tag to the head section of the delivered content:
<meta name="robots" content="noindex, nofollow">
Lets see if that helps.
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Assignee | ||
Comment 2•15 years ago
|
||
Bustage fix landed as:
http://hg.mozilla.org/qa/mozmill-tests/rev/06d676d1cae9
http://hg.mozilla.org/qa/mozmill-tests/rev/5e5cba320e6d
I have also updated all the Litmus tests.
Clint, please make sure we have a robots.txt or the meta line served for the tcm part on brasstacks.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•15 years ago
|
Whiteboard: [mozmill-test-failure]
Updated•8 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•