44
edits
WebExtensions/Try Server: Difference between revisions
Remove e10s suffix; add 1proc suffix - see https://groups.google.com/d/msg/mozilla.dev.platform/BrMY8dqogAY/3kTfrIjOCQAJ
(Show more efficient try syntax in examples) |
(Remove e10s suffix; add 1proc suffix - see https://groups.google.com/d/msg/mozilla.dev.platform/BrMY8dqogAY/3kTfrIjOCQAJ) |
||
| Line 12: | Line 12: | ||
Symbols for the following [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing#In_production test suites] are shown in the test results on Treeherder. Test suite identifiers for use with "-t" in "mach try" are listed below the main bullet points: | Symbols for the following [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Automated_testing#In_production test suites] are shown in the test results on Treeherder. Test suite identifiers for use with "-t" in "mach try" are listed below the main bullet points: | ||
* M (mochitests) and M- | * M (mochitests) and M-1proc (mochitests in single-process mode) | ||
** mochitests (all mochitests, including many non-extension test suites). Not to be confused with "mochitest" (which only runs plain | ** mochitests (all mochitests, including many non-extension test suites). Not to be confused with "mochitest" (which only runs plain e10s mochitests). | ||
** mochitest-bc ([https://developer.mozilla.org/en-US/docs/Mozilla/Browser_chrome_tests browser chrome tests]; desktop only - Windows, Linux and macOS) | ** mochitest-bc ([https://developer.mozilla.org/en-US/docs/Mozilla/Browser_chrome_tests browser chrome tests]; desktop only - Windows, Linux and macOS) | ||
** mochitest-o (Android only) | ** mochitest-o (Android only) | ||
* X (xpcshell tests) | * X (xpcshell tests) and X-1proc (xpcshell tests in single-process mode) | ||
** xpcshell | ** xpcshell | ||
* TV ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Test_Verification test verification mode]; same effect as "mach test path/to/your/test --verify" locally) (desktop platforms only; not available on Android) | * TV ([https://developer.mozilla.org/en-US/docs/Mozilla/QA/Test_Verification test verification mode]; same effect as "mach test path/to/your/test --verify" locally) (desktop platforms only; not available on Android) | ||
** test-verify | ** test-verify | ||
* ES ([https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/ESLint ESlint]) | * ES ([https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/ESLint ESlint]) | ||
| Line 35: | Line 35: | ||
* Run all relevant tests. This is expensive and should only be used when you don't know which tests should be run, because it also includes many non-extension tests. | * Run all relevant tests. This is expensive and should only be used when you don't know which tests should be run, because it also includes many non-extension tests. | ||
<nowiki>mach try -b do -p win64,linux64,macosx64,android-api-16 -u mochitests,xpcshell,test-verify | <nowiki>mach try -b do -p win64,linux64,macosx64,android-api-16 -u mochitests,xpcshell,test-verify --artifact</nowiki> | ||
* Run all relevant tests, without non-extension tests. The command with the `--tag=webextensions` flag uses your local checkout and .mozconfig configuration to identify the tests. Some Android-only tests may not run if your current configuration targets desktop. | * Run all relevant tests, without non-extension tests. The command with the `--tag=webextensions` flag uses your local checkout and .mozconfig configuration to identify the tests. Some Android-only tests may not run if your current configuration targets desktop. | ||
<nowiki>mach try -b do -p win64,linux64,macosx64,android-api-16 -u test-verify | <nowiki>mach try -b do -p win64,linux64,macosx64,android-api-16 -u test-verify --artifact --tag=webextensions</nowiki> | ||
* Run browser-chrome extension tests (and many other browser-chrome tests, but at least less expensive than just "mochitests"). This test type is only used on desktop, so Android was omitted from the platform flag ("-p"). | * Run browser-chrome extension tests (and many other browser-chrome tests, but at least less expensive than just "mochitests"). This test type is only used on desktop, so Android was omitted from the platform flag ("-p"). | ||
<nowiki>mach try -b do -p win64,linux64,macosx64 -u mochitest-bc,test-verify | <nowiki>mach try -b do -p win64,linux64,macosx64 -u mochitest-bc,test-verify --artifact</nowiki> | ||
* Run extension tests on Android (requires a [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_for_Android_build#Prepare_a_Firefox_for_Android_mozconfig_file mozconfig file for Android]; otherwise tests in mobile/android/components/extensions/test/ will not be run. The MOZCONFIG environment variable is used to select a different mozconfig file, so that you can develop for multiple platforms with a single checkout): | * Run extension tests on Android (requires a [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Build_Instructions/Simple_Firefox_for_Android_build#Prepare_a_Firefox_for_Android_mozconfig_file mozconfig file for Android]; otherwise tests in mobile/android/components/extensions/test/ will not be run. The MOZCONFIG environment variable is used to select a different mozconfig file, so that you can develop for multiple platforms with a single checkout): | ||
<nowiki>MOZCONFIG=/path/to/mozconfig-for-android mach try -b do -p android-api-16 --artifact --tag=webextensions</nowiki> | <nowiki>MOZCONFIG=/path/to/mozconfig-for-android mach try -b do -p android-api-16 --artifact --tag=webextensions</nowiki> | ||