gecko-dev/testing/profiles/profiles.json

{
    "geckoview-junit": ["base", "common", "unittest-required", "unittest-features", "geckoview-junit"],
    "mochitest": ["base", "common", "unittest-required", "unittest-features", "mochitest"],
    "profileserver": ["base", "common", "unittest-required", "unittest-features", "profileserver"],
    "raptor": ["base", "common", "perf", "raptor"],
    "reftest": ["base", "common", "reftest"],
    "talos": ["base", "common", "perf"],
    "valgrind": ["base", "common", "unittest-required", "unittest-features"],
    "xpcshell": ["base", "xpcshell"],
    "web-platform-tests": ["base", "common", "unittest-required", "unittest-features", "web-platform"]
}
Bug 1459598 - Use profiles.json file to map test suites to the base profiles they use, r=jgraham This serves two purposes: 1) It makes web-platform-tests pref downloading/handling a little more robust. When run externally, it now downloads the entire testing/profiles directory. When loading prefs it will look for both prefs_general.js (to support older versions of Firefox) and profiles.json (for support moving forward). This way we can add/remove/rename pref files under these directories without needing to worry about breaking upstream wpt. 2) It provides developers an overview of which harnesses are using which base profiles. Instead of hunting through test harness code to find this information, they can glance at profiles.json. MozReview-Commit-ID: AMzdnD8aGA2 --HG-- extra : rebase_source : 6fa0a802680417e49fcef99f3d03de7458a8fcba 2018-05-07 16:43:12 +03:00			`{`
Bug 1604212 - Enable sameSite=lax by default, r=Ehsan,ahal Differential Revision: https://phabricator.services.mozilla.com/D63081 --HG-- extra : moz-landing-system : lando 2020-02-27 07:38:03 +03:00			`"geckoview-junit": ["base", "common", "unittest-required", "unittest-features", "geckoview-junit"],`
			`"mochitest": ["base", "common", "unittest-required", "unittest-features", "mochitest"],`
Bug 1485386 - Move feature-enabling preferences out of unittest/user.js into a separate file r=ahal The unittest/user.js file contained a mix of preferences that ensure tests can run (switching web services to dummy servers to prevent hitting networks, etc) and preferences that enable features that aren't shipping by default (turning on touch events, enabling experimental css features, etc). In the future, we're going to want to run tests of only the features that are being shipped in release builds (or in beta builds, or in esr builds, etc), so we need to move feature-enabling preferences into a different file to make it possible to run tests with various sets of features enabled. This commit just moves feature-enabling prefs into a new file and then includes that file everywhere unittest prefs were already being included, so it should have no functional difference in the set of preferences being set in test runs. It also renames the unittest profile to clarify its purpose, and adds pointers to each profile from the other, and adds comments explaining what they're used for. Differential Revision: https://phabricator.services.mozilla.com/D16123 --HG-- rename : testing/profiles/unittest/extensions/README.txt => testing/profiles/unittest-features/extensions/README.txt rename : testing/profiles/unittest/extensions/README.txt => testing/profiles/unittest-required/extensions/README.txt rename : testing/profiles/unittest/user.js => testing/profiles/unittest-required/user.js extra : moz-landing-system : lando 2019-01-18 03:35:43 +03:00			`"profileserver": ["base", "common", "unittest-required", "unittest-features", "profileserver"],`
Bug 1460914 - [xpcshell] Define preferences in testing/profiles instead of testing/xpcshell/head.js, r=ted This commit creates an empty 'base' profile because I wanted to preserve the ability to apply a pref to all test harnesses on try. Since xpcshell doesn't share many prefs with the other harnesses, it can't use the common profile. So adding a pref to 'common' will apply it everywhere except xpcshell. Adding a pref to 'base' will apply it everywhere including xpcshell. These profiles are starting to get a bit messy, but I'd like to punt re-organizing them to a follow-up bug. Depends on D9716 Differential Revision: https://phabricator.services.mozilla.com/D9717 --HG-- extra : moz-landing-system : lando 2018-10-26 20:47:18 +03:00			`"raptor": ["base", "common", "perf", "raptor"],`
			`"reftest": ["base", "common", "reftest"],`
			`"talos": ["base", "common", "perf"],`
Bug 1485386 - Move feature-enabling preferences out of unittest/user.js into a separate file r=ahal The unittest/user.js file contained a mix of preferences that ensure tests can run (switching web services to dummy servers to prevent hitting networks, etc) and preferences that enable features that aren't shipping by default (turning on touch events, enabling experimental css features, etc). In the future, we're going to want to run tests of only the features that are being shipped in release builds (or in beta builds, or in esr builds, etc), so we need to move feature-enabling preferences into a different file to make it possible to run tests with various sets of features enabled. This commit just moves feature-enabling prefs into a new file and then includes that file everywhere unittest prefs were already being included, so it should have no functional difference in the set of preferences being set in test runs. It also renames the unittest profile to clarify its purpose, and adds pointers to each profile from the other, and adds comments explaining what they're used for. Differential Revision: https://phabricator.services.mozilla.com/D16123 --HG-- rename : testing/profiles/unittest/extensions/README.txt => testing/profiles/unittest-features/extensions/README.txt rename : testing/profiles/unittest/extensions/README.txt => testing/profiles/unittest-required/extensions/README.txt rename : testing/profiles/unittest/user.js => testing/profiles/unittest-required/user.js extra : moz-landing-system : lando 2019-01-18 03:35:43 +03:00			`"valgrind": ["base", "common", "unittest-required", "unittest-features"],`
Bug 1460914 - [xpcshell] Define preferences in testing/profiles instead of testing/xpcshell/head.js, r=ted This commit creates an empty 'base' profile because I wanted to preserve the ability to apply a pref to all test harnesses on try. Since xpcshell doesn't share many prefs with the other harnesses, it can't use the common profile. So adding a pref to 'common' will apply it everywhere except xpcshell. Adding a pref to 'base' will apply it everywhere including xpcshell. These profiles are starting to get a bit messy, but I'd like to punt re-organizing them to a follow-up bug. Depends on D9716 Differential Revision: https://phabricator.services.mozilla.com/D9717 --HG-- extra : moz-landing-system : lando 2018-10-26 20:47:18 +03:00			`"xpcshell": ["base", "xpcshell"],`
Bug 1485386 - Move feature-enabling preferences out of unittest/user.js into a separate file r=ahal The unittest/user.js file contained a mix of preferences that ensure tests can run (switching web services to dummy servers to prevent hitting networks, etc) and preferences that enable features that aren't shipping by default (turning on touch events, enabling experimental css features, etc). In the future, we're going to want to run tests of only the features that are being shipped in release builds (or in beta builds, or in esr builds, etc), so we need to move feature-enabling preferences into a different file to make it possible to run tests with various sets of features enabled. This commit just moves feature-enabling prefs into a new file and then includes that file everywhere unittest prefs were already being included, so it should have no functional difference in the set of preferences being set in test runs. It also renames the unittest profile to clarify its purpose, and adds pointers to each profile from the other, and adds comments explaining what they're used for. Differential Revision: https://phabricator.services.mozilla.com/D16123 --HG-- rename : testing/profiles/unittest/extensions/README.txt => testing/profiles/unittest-features/extensions/README.txt rename : testing/profiles/unittest/extensions/README.txt => testing/profiles/unittest-required/extensions/README.txt rename : testing/profiles/unittest/user.js => testing/profiles/unittest-required/user.js extra : moz-landing-system : lando 2019-01-18 03:35:43 +03:00			`"web-platform-tests": ["base", "common", "unittest-required", "unittest-features", "web-platform"]`
Bug 1459598 - Use profiles.json file to map test suites to the base profiles they use, r=jgraham This serves two purposes: 1) It makes web-platform-tests pref downloading/handling a little more robust. When run externally, it now downloads the entire testing/profiles directory. When loading prefs it will look for both prefs_general.js (to support older versions of Firefox) and profiles.json (for support moving forward). This way we can add/remove/rename pref files under these directories without needing to worry about breaking upstream wpt. 2) It provides developers an overview of which harnesses are using which base profiles. Instead of hunting through test harness code to find this information, they can glance at profiles.json. MozReview-Commit-ID: AMzdnD8aGA2 --HG-- extra : rebase_source : 6fa0a802680417e49fcef99f3d03de7458a8fcba 2018-05-07 16:43:12 +03:00			`}`