Open
Description
What is this about?
Recently a number of E2E test jobs were made optional on PRs. They are now only triggered on long-running branches.
We should add a way to manually trigger these jobs, in case a PR is expected to have some impact upon them. For example, if we fix a test related to Firefox, we should run the Firefox E2E tests before merging.
Scenario
No response
Design
No response
Technical Details
No response
Threat Modeling Framework
No response
Acceptance Criteria
No response
Stakeholder review needed before the work gets merged
- Engineering (needed in most cases)
- Design
- Product
- QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- Security
- Legal
- Marketing
- Management (please specify)
- Other (please specify)
References
No response