Confirmed users
964
edits
QA/External Tests: Difference between revisions
Jump to navigation
Jump to search
→Proposal
No edit summary |
|||
| Line 11: | Line 11: | ||
== Proposal == | == Proposal == | ||
To solve this, let's create an directory named 'external' in Gecko and Gaia, specifically for tests with external access that will not be run by the releng/buildbot system or the standard make targets. | To solve this, let's create an directory named 'external' in Gecko and Gaia, specifically for tests with external access that will not be run by the releng/buildbot system or the standard make targets. Implement support for these tests in mach/make with a specific flag for local execution and non tinderbox CI. | ||
These tests will: | These tests will: | ||
* NOT run on the releng/buildbot system | * NOT run on the releng/buildbot system. Tests will be run on another CI system. | ||
* NOT run | * NOT run by default make/mach test commands. | ||
* | * Will required a flag to execute | ||
* Test reports will be sent to TreeHerder | * Test reports will be sent to TreeHerder | ||
* Devs can choose to run these tests locally when they are on the internet and are working on code that affects that service. | * Devs can choose to run these tests locally when they are on the internet and are working on code that affects that service. | ||
* Environment variables will be set to direct tests to point to {PROD,STAGE,DEV} servers. | * Environment variables will be set to direct tests to point to {PROD,STAGE,DEV} servers. | ||
=== Details === | |||
* land tests in a directory name "external" so it's easily identified as needing external access. | |||
* implement support in test manifest and mach/make to enable execution of external tests only (default would be not to run external tests) | |||
=== Examples === | === Examples === | ||