Closed Bug 1737670 Opened 3 years ago Closed 3 years ago

Add an additional mochitest manifest to run service worker tests with dFPI enabled

Categories

(Core :: Privacy: Anti-Tracking, enhancement)

enhancement

Tracking

()

RESOLVED FIXED
96 Branch
Tracking Status
firefox96 --- fixed

People

(Reporter: timhuang, Assigned: timhuang)

References

Details

Attachments

(4 files)

To verify the service worker with dFPI, we can add an additional mochitest manifest which flips the pref and run the service worker tests. Here is an example of how we can achieve this.

The goal of this bug is to create the manifest and start to run service worker tests that can work with dFPI already. The final goal is to run all service worker tests with dFPI.

Assignee: nobody → tihuang
Status: NEW → ASSIGNED

In order to support running service worker tests for dFPI, we first
convert the existing mochitest.ini, chrome.ini and browser.ini to
mochitest-common.ini, chrome-common.ini and browser-common.ini respectively.
And create ini files that import them.

Currently, the third-party service worker is disabled in dFPI. So, it
makes no sense to run xorigin tests for dFPI.

Depends on D130747

Pushed by tihuang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/470f1a878913
Part 1: Convert the existing mochitest ini files to mochitest common ini files in service worker tests. r=asuth
https://hg.mozilla.org/integration/autoland/rev/a49b573e4aea
Part 2: Add ini files for testing service worker tests with dFPI. r=asuth
https://hg.mozilla.org/integration/autoland/rev/cf41ca834450
Part 3: Moving tests that are not compatible with dFPI to mochitest.ini from mochitest-common.init. r=asuth
https://hg.mozilla.org/integration/autoland/rev/fb07dd74e93a
Part 4: Skip xorigin test for dFPI in serviceworkers. r=asuth
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: