testing/profiles/profiles.json
author Wes Kocher <wkocher@mozilla.com>
Fri, 18 Jan 2019 00:35:43 +0000
changeset 511472 0e2384b8497dbe5af4db59a7b8be7241caf7266d
parent 511270 f59ff936f6a2154c2048b5bf397c4751a3a593b5
permissions -rw-r--r--
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

{
    "mochitest": ["base", "common", "unittest-required", "unittest-features"],
    "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"]
}