QA/Polaris/Tracking protection: Difference between revisions

m
Line 35: Line 35:


=== Full ===
=== Full ===
* Marionette test https://bugzilla.mozilla.org/show_bug.cgi?id=1148101
Complete all tests with both old and new (fresh) profile
* Block/unblock sites
 
* Reset/site management
* With normal browsing:
* UI
** View URL with tracking elements and verify not blocked
 
* With private browsing:
** View URL with tracking elements and verify blocked
** Add exception for page
** Reblock page
** Add exception for page again
** Return to normal browsing and verify page NOT blocked
 
* With private browsing:
** Verify UI tour appears on first launch, does not appear on subsequent launches
** Verify tour functionality
 
* Preferences
** Turn on/off
** List providers
 
* Cases
** Tracked asset
** Tracked asset and active mixed content
** Tracked asset and passive mixed content
** Tracked asset and both active/passive mixed content
** Add exception for page, navigate to different page with same tracker
** Tracked asset in iframe
** Page with multiple tracked assets
 
* Opening private browsing
** File > New private window
** Keyboard shortcut
 
* Scenarios
** Same page in both private/non-private windows
** Multiple tabs -- TBD
** Interaction with AdBlockPlus, Disconnect, other add-ons
** Disable safe browsing, verify tracking protection is still enabled
 
* List management
* List management
** stale
** Add/remove entries
** update
** Stale list
* Entity list
** Entity management
* Shavar server  
 
** TBD, coordinate with rpapa
* Shavar server
** Add/remove chunks
** TBD, with rpapa
** Load testing
 
** APIs
* Community
** Functional tests
** One and Done task
** Do we need test URLs in shavar to test blocking logic?
 
* Review bugs for possible edge case tests
* Automation
** Disable safe browsing disables TP
** Marionette test https://bugzilla.mozilla.org/show_bug.cgi?id=1148101
 
* Misc
** about:privatebrowsing


=== Community ===
=== Community ===
Confirmed users
651

edits