Services/TrackingProtection/Shavar Server - Testing: Difference between revisions

Jump to navigation Jump to search
m
Re-organize test cases
m (Move setup to a separate section)
m (Re-organize test cases)
Line 95: Line 95:


'''List Delivery and Creation Test'''
'''List Delivery and Creation Test'''
* follow [[#Setup_.231|Setup #1]]  instructions (create new profile, set prefs!)
* Follow [[#Setup|Setup]]  instructions (create new profile, set prefs!)
* do cache file sanity checks ([[#TEST_.230:_verify_downloaded_.28cached.29_mozpub_list_files|TEST #0]]) with unchanged black/white lists.
* Do cache file sanity checks ([[#TEST_.230:_verify_downloaded_.28cached.29_mozpub_list_files|TEST #0]]) with unchanged black/white lists.


'''Additions/Deletions Test'''
'''Additions/Deletions Test'''
* follow [[#Setup_.232|Setup #1]] instructions  (create new prof, set different prefs)
* Follow [[#Setup|Setup]] instructions  (create new profile, set different prefs)
* do cache file sanity checks ([[#TEST_.230:_verify_downloaded_.28cached.29_moztestpub_list_files|TEST #0]])
* Do cache file sanity checks ([[#TEST_.230:_verify_downloaded_.28cached.29_moztestpub_list_files|TEST #0]])
* Verify that blacklist and whitelist updates get properly delivered to client
* Verify that blacklist and whitelist updates get properly delivered to client


Line 107: Line 107:


* ideally we'd be using the real list  
* ideally we'd be using the real list  
** we can do that for almost all the e2e test and validation test, but we can't do that for the "update" test
** we can do that for almost all the end-2-end and validation tests, but we can't do that for the "update" test
* TEST #0 gets executed twice  
* TEST #0 gets executed twice  
** once w/  [[#Setup_.231|Setup #1]] to verify mozstd, mozfull cache files
** once w/  [[#Setup|Setup]] to verify moztestpub, mozstd, mozfull cache files
** once w/  [[#Setup_.232|Setup #2]] to verify mozstd, mozfull cache files
** once w/  [[#Setup|Setup]] to verify moztestpub cache files


[[#top]]
[[#top]]
Line 251: Line 251:


* !!!!!  restart Firefox !!!!!!
* !!!!!  restart Firefox !!!!!!


Replace production URL with stage URL for the following prefs:
Replace production URL with stage URL for the following prefs:
Line 271: Line 270:
[[#top]]
[[#top]]


== List Delivery & Creation Tests ==
== List Delivery & Creation Tests (moztestpub, mozstd, mozfull) ==
 
=== list delivery ===
 
TEST #0


=== Summary ===
Verify that all data lists have been delivered and have a reasonable filesize.
These tests are executed once for each data list
Execute the following tests, once for each data list.


* moztestpub
* moztestpub
Line 280: Line 283:
* mozfull
* mozfull


=== Setup ===  
=== verify list files cache ===  
xxx


=== TEST #0.1: verify list files download / cache ===
'''SETUP'''
Follow setup instructions for all three list files here: [[#Setup|Setup]]


'''SUMMARY'''
'''SUMMARY'''
Line 348: Line 351:
</code>
</code>


=== TEST #0.2: verify its-a-tracker page ===  
=== verify its-a-tracker page ===  


* Pull up this page: http://itisatrap.org/firefox/its-a-tracker.html  
* Pull up this page: http://itisatrap.org/firefox/its-a-tracker.html  
Line 356: Line 359:
* If not working, then either about:config issue or client issue - repeat above!
* If not working, then either about:config issue or client issue - repeat above!


=== TEST #0.3: verify CNN page ===  
=== verify CNN page ===  


* Pull up CNN: http://www.cnn.com
* Pull up CNN: http://www.cnn.com
Line 362: Line 365:
* the developer tool console tab should indicate that something was blocked by tracking protection - should say something like URL blocked because of tracking
* the developer tool console tab should indicate that something was blocked by tracking protection - should say something like URL blocked because of tracking


=== TEST #0.4: verify YouTube page ===  
=== verify YouTube page ===  


* Pull up Youtube: https://www.youtube.com
* Pull up Youtube: https://www.youtube.com
Line 371: Line 374:
[[#top]]
[[#top]]


== List Additions / Deletions Tests (moztestpub only!) ==
== List Additions / Deletions Tests (moztestpub) ==


=== Setup #2 ===  
=== blacklist deletions ===
'''SUMMARY'''
* We start with the same custom prefs we set in [[#Setup_.231|Setup #1]].


[[#top]]
TEST #1


=== TEST #1: verify blacklist deletions ===  
==== verify enabled ====  
 
'''VERIFY ENABLED'''


* Follow setup instructions for moztestpub file here: [[#Setup|Setup]]
* Pull up this test page: https://people.mozilla.org/~fmarier/tracking-test/
* Pull up this test page: https://people.mozilla.org/~fmarier/tracking-test/
* ensure that the resource is blocked:
* ensure that the resource is blocked:
Line 390: Line 390:
** A message in the: Tools > Web Developer > Browser Console: "The resource at "https://extremetracking.com/" was blocked because tracking protection is enabled."  
** A message in the: Tools > Web Developer > Browser Console: "The resource at "https://extremetracking.com/" was blocked because tracking protection is enabled."  


'''DELETE FROM LIST'''
==== delete from blacklist ====


* Follow setup instructions for moztestpub file here: [[#Setup|Setup]]
* Remove the extremetracking.com json blob from the blacklist on https://github.com/mozilla-services/shavar-test-lists
* Remove the extremetracking.com json blob from the blacklist on https://github.com/mozilla-services/shavar-test-lists
* This will trigger the stage list creation script (Cloud Services QA or Ops team can monitor this in Jenkins)
* This will trigger the stage list creation script (Cloud Services QA or Ops team can monitor this in Jenkins)


'''VERIFY DISABLED'''
==== verify disabled ====
 
Start Debuggging
* Restart Firefox from terminal  to force list updates on client
* The pref set in STEP #0 (browser.safebrowsing.debug) will output debug messages like so: https://pastebin.mozilla.org/8844272
* Debug output will start in terminal 10 - 30 secs after you start browser


Verify:
* Start Debuggging
** Restart Firefox from terminal to force list updates on client
** The pref set in STEP #0 (browser.safebrowsing.debug) will output debug messages like so: https://pastebin.mozilla.org/8844272
** Debug output will start in terminal 10 - 30 secs after you start browser
* update URL has registered correctly (line #8)
* update URL has registered correctly (line #8)
** Registering whitelist- mozpub-trackwhite-digest256 (line #10)
** Registering whitelist- mozpub-trackwhite-digest256 (line #10)
Line 413: Line 412:
[[#top]]
[[#top]]


=== TEST #2: verify blacklist additions ===  
=== blacklist additions ===  


'''ADD TO LIST'''
TEST #2
 
==== add to blacklist ====


* Add the extremetracking.com json blob back to the blacklist on https://github.com/mozilla-services/shavar-test-lists
* Add the extremetracking.com json blob back to the blacklist on https://github.com/mozilla-services/shavar-test-lists
* This will trigger the stage list creation script (Cloud Services QA or Ops team can monitor this in Jenkins)
* This will trigger the stage list creation script (Cloud Services QA or Ops team can monitor this in Jenkins)


 
==== verify enabled ====
'''VERIFY RE-ENABLED'''


* check that it's blocked again by visiting https://people.mozilla.org/~fmarier/tracking-test/
* check that it's blocked again by visiting https://people.mozilla.org/~fmarier/tracking-test/
Line 428: Line 428:
[[#top]]
[[#top]]


=== TEST #3: verify whitelist deletions  ===  
=== whitelist deletions  ===  
 
TEST #3


'''SUMMARY'''
'''SUMMARY'''
Line 436: Line 438:
* By removing it from whitelist, we should be able to verify that it now gets blocked!
* By removing it from whitelist, we should be able to verify that it now gets blocked!


'''VERIFY ENABLED'''
==== verify enabled ====


Start Debuggging
Start Debuggging
Line 443: Line 445:
* Debug output will start in terminal 10 - 30 secs after you start browser
* Debug output will start in terminal 10 - 30 secs after you start browser


'''REMOVE FROM WHITELIST'''
==== delete from whitelist ====


* Remove googlesyndication.com from the "Google" organization in the resources section of the whitelist - https://github.com/mozilla-services/shavar-test-lists  
* Remove googlesyndication.com from the "Google" organization in the resources section of the whitelist - https://github.com/mozilla-services/shavar-test-lists  
* This will trigger the stage list creation script (Cloud Services QA or Ops team can monitor this in Jenkins)
* This will trigger the stage list creation script (Cloud Services QA or Ops team can monitor this in Jenkins)


'''VERIFY DISABLED'''
==== verify disabled ====
 
* update URL has registered correctly (line #8)
* update URL has registered correctly (line #8)
** Registering whitelist- mozstd-trackwhite-digest256 (line #10) - or mozfull
** Registering whitelist- mozstd-trackwhite-digest256 (line #10) - or mozfull
Confirmed users
487

edits

Navigation menu