gecko-dev/testing/profiles/moz.build

# -*- Mode: python; indent-tabs-mode: nil; tab-width: 40 -*-
# vim: set filetype=python:
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, You can obtain one at http://mozilla.org/MPL/2.0/.

profile_files = [
    'common/*',
    'profiles.json',
]

TEST_HARNESS_FILES.testing.mochitest.profile_data += profile_files
TEST_HARNESS_FILES['web-platform'].prefs += profile_files

with Files("**"):
    BUG_COMPONENT = ("Testing", "General")
Bug 1286877 - do not set c-basic-offset for python-mode; r=gps This removes the unnecessary setting of c-basic-offset from all python-mode files. This was automatically generated using perl -pi -e 's/; c-basic-offset: [0-9]+//' ... on the affected files. The bulk of these files are moz.build files but there a few others as well. MozReview-Commit-ID: 2pPf3DEiZqx --HG-- extra : rebase_source : 0a7dcac80b924174a2c429b093791148ea6ac204 2016-07-14 19:16:42 +03:00			`# -- Mode: python; indent-tabs-mode: nil; tab-width: 40 --`
Bug 835930 - move b2g unittest profile handling on top of mozbase instead of automation.py, r=jgriffin 2013-03-29 00:42:49 +04:00			`# vim: set filetype=python:`
			`# This Source Code Form is subject to the terms of the Mozilla Public`
			`# License, v. 2.0. If a copy of the MPL was not distributed with this`
			`# file, You can obtain one at http://mozilla.org/MPL/2.0/.`

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			`profile_files = [`
Bug 1451159 - [testing/profiles] Store profile data in actual profile look alike folders r=gbrown This moves testing/profiles/prefs_general.js to testing/profiles/common/user.js. It also adds an 'extensions' folder to the common profile. Dropping extension files here will get them installed in all test harnesses (useful for testing on try). The idea is that all test harnesses will eventually use this 'common' profile. We'll also create some new per harness profiles, e.g testing/profiles/mochitest and testing/profiles/reftest. This way there will be a single location developers can go to set preferences, both for a specific harness, and across all harnesses. MozReview-Commit-ID: 8sqBqLiypgU --HG-- rename : testing/profiles/prefs_general.js => testing/profiles/common/user.js extra : rebase_source : 72a4a4b691e93c77479c7e70647b0ca373862c51 2018-04-19 23:12:26 +03:00			`'common/*',`
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			`'profiles.json',`
Bug 1109831 - move testing/profiles/ files to moz.build's TEST_HARNESS_FILES; r=mshal 2014-12-10 21:58:51 +03:00			`]`

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			`TEST_HARNESS_FILES.testing.mochitest.profile_data += profile_files`
			`TEST_HARNESS_FILES['web-platform'].prefs += profile_files`
Bug 1326465 - add BUG_COMPONENTS to testing/. r=gbrown,ted ensuring moz.build files have BUG_COMPONENTS for all files in the testing/ subdirectory is a win. There are a lot of older files and some files used in many harnesses. If the files are primarily used for mochitest, they are associated with the testing::mochitest component, otherwise I chose the testing::general component. There is an exception web-platform-tests, these have many test files that need to be matched to proper components. MozReview-Commit-ID: IIv9W2kEqeN 2016-12-31 00:16:56 +03:00
			`with Files("**"):`
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_COMPONENT = ("Testing", "General")`