diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-04-09 18:09:10 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-04-09 18:09:10 +0300 |
| commit | 9ea69b43c3502c4c63e6d47da40786875197fcf3 (patch) | |
| tree | 34a74f05ff8321a9dc16bb22dd3d3fe6ef55d3e7 /.gitlab/merge_request_templates | |
| parent | 45c999c8bcab0cd8ea766919634580465e5080d9 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to '.gitlab/merge_request_templates')
| -rw-r--r-- | .gitlab/merge_request_templates/Quarantine End to End Test.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/.gitlab/merge_request_templates/Quarantine End to End Test.md b/.gitlab/merge_request_templates/Quarantine End to End Test.md index cf0a89284ae..5794a62df96 100644 --- a/.gitlab/merge_request_templates/Quarantine End to End Test.md +++ b/.gitlab/merge_request_templates/Quarantine End to End Test.md @@ -3,7 +3,7 @@ <!-- Please describe why the end-to-end test is being quarantined/ de-quarantined. -Please note that the aim of quarantining a test is not to get back a green pipeline, but rather to reduce +Please note that the aim of quarantining a test is not to get back a green pipeline, but rather to reduce the noise (due to constantly failing tests, flaky tests, and so on) so that new failures are not missed. --> @@ -24,15 +24,15 @@ the noise (due to constantly failing tests, flaky tests, and so on) so that new - [ ] Note if the test should be [quarantined for a specific environment](https://docs.gitlab.com/ee/development/testing_guide/end_to_end/environment_selection.html#quarantining-a-test-for-a-specific-environment). - [ ] Dequarantine test check-list - [ ] Follow the [Dequarantining Tests guide](https://about.gitlab.com/handbook/engineering/quality/guidelines/debugging-qa-test-failures/#dequarantining-tests). - - [ ] Confirm the test consistently passes on the target GitLab environment(s). - - [ ] (Optionally) [Trigger a manual GitLab-QA pipeline](https://about.gitlab.com/handbook/engineering/quality/guidelines/tips-and-tricks/#running-gitlab-qa-pipeline-against-a-specific-gitlab-release) against a specific GitLab environment using the `RELEASE` variable from the `package-and-qa` job of the current Merge Request. -- [ ] To ensure a faster turnaround, ask in the `#quality` Slack channel for someone to review and merge the merge request, rather than assigning it directly. + - [ ] Confirm the test consistently passes on the target GitLab environment(s). + - [ ] (Optionally) [Trigger a manual GitLab-QA pipeline](https://about.gitlab.com/handbook/engineering/quality/guidelines/tips-and-tricks/#running-gitlab-qa-pipeline-against-a-specific-gitlab-release) against a specific GitLab environment using the `RELEASE` variable from the `package-and-qa` job of the current merge request. +- [ ] To ensure a faster turnaround, ask in the `#quality` Slack channel for someone to review and merge the merge request, rather than assigning it directly. <!-- Base labels. --> -/label ~"Quality" ~"QA" ~"feature" ~"feature::maintenance" +/label ~"Quality" ~"QA" ~"feature" ~"feature::maintenance" <!-- Labels to pick into auto-deploy. --> -/label ~"Pick into auto-deploy" ~"priority::1" ~"severity::1" +/label ~"Pick into auto-deploy" ~"priority::1" ~"severity::1" <!-- Choose the stage that appears in the test path, e.g. ~"devops::create" for |