Open Bug 1239158 Opened 9 years ago Updated 2 years ago

Write a Marionette test that checks that visiting a website with a tracker in Private Browsing blocks the tracker

Categories

(Toolkit :: Safe Browsing, defect)

defect

Tracking

()

People

(Reporter: francois, Unassigned)

References

(Blocks 1 open bug)

Details

The simplest way to do this is to visit http://cnn.com and check that the shield shows up. Alternatively, we could get Disconnect to add a tracking domain (we own itisatracker.com but currently don't use it) to their list and then setup a test page somewhere that loads http://itisatracker.com/tracker.js
Component: DOM: Security → Firefox UI Tests
Product: Core → Testing
QA Contact: hskupin
I'm not that hesitated to have a test utilizing cnn.com, so I really would prefer the second option. Especially because its under own control.
(In reply to Henrik Skupin (:whimboo) from comment #1) > I'm not that hesitated to have a test utilizing cnn.com, so I really would > prefer the second option. Especially because its under own control. You mentioned mozqa.com in a different bug. What's the process to get a test page hosted there?
Flags: needinfo?(hskupin)
If you only have a test file which needs to be uploaded you can add it via: http://hg.mozilla.org/qa/testcase-data/ We sync automatically the changes each 15min. There simply file a bug in Mozilla QA / Infrastructure and upload the patch. If IT needs to be involved because low level changes have to be made, we will create dependent bugs.
Flags: needinfo?(hskupin)
Assignee: nobody → mwobensmith
My test page is now live at https://www.mozqa.com/data/firefox/safebrowsing/trackingprotection.html and relies on an entry that got added to the Disconnect list.
Thanks Francois, just a fyi... similar to each check-in we also do reviews on testcase data. So if there is something else you want to upload please let it go through the review process. Thanks.
I assume that Matt doesn't mind if someone else takes care of this.
Assignee: mwobensmith → nobody
I do not mind. Sorry for not being able to do anything about it. :(

Would this still be something helpful to have? Moving to the safebrowsing component because developers would have to take care of it.

Component: Firefox UI Tests → Safe Browsing
Product: Testing → Toolkit
QA Contact: hskupin
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.