gecko-dev/testing/profiles/profiles.json

{
    "mochitest": ["common", "unittest"],
    "profileserver": ["common", "unittest", "profileserver"],
    "raptor": ["common", "perf", "raptor"],
    "reftest": ["common", "reftest"],
    "talos": ["common", "perf"],
    "valgrind": ["common", "unittest"],
    "web-platform-tests": ["common", "unittest", "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 1458571 - Make talos and raptor use the 'common' base profile, r=rwood This factors out the prefs that are common across raptor, talos and mochitest/web-platform-tests. In order to do this a new "unittest" profile has been created. This means, to set a pref across everything that uses this system, edit: testing/profiles/common/user.js To set a pref across unittest frameworks (which excludes raptor and talos), edit: testing/profiles/unittest/user.js Setting a pref for perf frameworks only remains the same. Extensions follow the same rules (drop them in <profile>/extensions). MozReview-Commit-ID: 6AHlYsN0Lb8 --HG-- extra : rebase_source : aad259f06af549f3bc707fed5b1caaacf25bc28f 2018-05-10 22:31:31 +03:00			`"mochitest": ["common", "unittest"],`
Bug 905404 - [pgo] Add custom profile data in testing/profiles/profileserver. r=ahal Add extra preferences for the profileserver script on-top of the ones as inheritted from unittests. --HG-- extra : rebase_source : 02d3297134e82c2425fc4c6c939cc5d0cc4a2c13 extra : histedit_source : 07f699b0ff8bec2a6eda7705a0fa13fb3b352f98 2018-09-06 09:47:46 +03:00			`"profileserver": ["common", "unittest", "profileserver"],`
Bug 1458571 - Make talos and raptor use the 'common' base profile, r=rwood This factors out the prefs that are common across raptor, talos and mochitest/web-platform-tests. In order to do this a new "unittest" profile has been created. This means, to set a pref across everything that uses this system, edit: testing/profiles/common/user.js To set a pref across unittest frameworks (which excludes raptor and talos), edit: testing/profiles/unittest/user.js Setting a pref for perf frameworks only remains the same. Extensions follow the same rules (drop them in <profile>/extensions). MozReview-Commit-ID: 6AHlYsN0Lb8 --HG-- extra : rebase_source : aad259f06af549f3bc707fed5b1caaacf25bc28f 2018-05-10 22:31:31 +03:00			`"raptor": ["common", "perf", "raptor"],`
Bug 1460912 - [testing/profiles] Use the 'common' profile in reftest r=gbrown This removes prefs that are already shared between reftest and the 'common' profile from: testing/profiles/reftest/user.js And moves prefs that were set in the 'common' profile but not reftest to both: testing/profiles/unittest/user.js testing/profiles/perf/user.js MozReview-Commit-ID: HLfVrd2eD0l --HG-- extra : rebase_source : ff186d28fa9bb081133bec06ee6689d59e66d41e 2018-05-14 17:56:41 +03:00			`"reftest": ["common", "reftest"],`
Bug 1458571 - Make talos and raptor use the 'common' base profile, r=rwood This factors out the prefs that are common across raptor, talos and mochitest/web-platform-tests. In order to do this a new "unittest" profile has been created. This means, to set a pref across everything that uses this system, edit: testing/profiles/common/user.js To set a pref across unittest frameworks (which excludes raptor and talos), edit: testing/profiles/unittest/user.js Setting a pref for perf frameworks only remains the same. Extensions follow the same rules (drop them in <profile>/extensions). MozReview-Commit-ID: 6AHlYsN0Lb8 --HG-- extra : rebase_source : aad259f06af549f3bc707fed5b1caaacf25bc28f 2018-05-10 22:31:31 +03:00			`"talos": ["common", "perf"],`
			`"valgrind": ["common", "unittest"],`
Bug 905404 - [wpt] Add custom profile data in testing/profiles/web-platform. r=jgraham Add extra preferences for web-platform-tests on-top of the ones as inheritted from unittests. --HG-- extra : rebase_source : 6a1f6828eb52120f9a2029be8220931cd2ca0f69 extra : histedit_source : 5f219cbd34039c79c624bee35f3b56700bde903e 2018-09-06 09:44:52 +03:00			`"web-platform-tests": ["common", "unittest", "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			`}`