Implement a test plan for double key cookie logic
Write a test plan including unit and regression testing, and simplifying QA while supporting reuse.
3rd party consumer and provider hosts
For purposes of analysis (R&D) and validation (QA), implement a real world (as mcs puts it) test harness by configuring at least two divergent (according to RFC6265 5.1.3. Domain Matching) virtual hosts consuming 3rd party content. Implement a cookie provider serving HTTP headers in a 3rd party context (as a IFrame for example.)
Popular website tests
Write verification tests of a set of popular websites consuming 3rd party cookies to prove correct isolation via 1st party contexts. Specify a subset of web application use cases of 3rd party cookies (federated login, shopping cart, gaming) as well as a list of websites for each set.
Regression tests
Implement automated test scripts (possibly using either Mozilla XPCShell or Mochitest) for regression testing. Review #13749 (moved) for possible overlap.
Unit tests
Write unit tests (possibly hand typing in the JavaScript browser console) for individual components like host domain matching, cookie searches, cookie blocking, and privacy.thirdparty.isolate condition.
Optional unit tests
Optionally write unit tests (possibly using QUnitJS) for individual components.
Optional peripheral tests
Optionally integrate tests for #3600 (moved), leverage ideas from #3546 (moved) and #3676 (closed), and avoid redundancy with #13749 (moved).
Optional addon review
Get cozy with Cookie Monster #4132 (moved) and other Firefox addons to optionally broaden the scope of tests.
Trac:
Username: michael