2.3 KiB
2.3 KiB
Description of the test
Check-list
- Confirm the test has a
testcase:tag linking to an existing test case in the test case project. - Note if the test is intended to run in specific scenarios. If a scenario is new, add a link to the MR that adds the new scenario.
- Follow the end-to-end tests style guide and best practices.
- Use the appropriate RSpec metadata tag(s).
- Ensure that a created resource is removed after test execution. A
Groupresource can be shared between multiple tests. Do not remove it unless it has a unique path. Note that we have a cleanup job that periodically removes groups undergitlab-qa-sandbox-group. - Ensure that no transient bugs are hidden accidentally due to the usage of
waitsandreloads. - Verify the tags to ensure it runs on the desired test environments.
- If this MR has a dependency on another MR, such as a GitLab QA MR, specify the order in which the MRs should be merged.
- (If applicable) Create a follow-up issue to document the special setup necessary to run the test: ISSUE_LINK
- If the test requires an admin's personal access token, ensure that the test passes on your local with and without the
GITLAB_QA_ADMIN_ACCESS_TOKENprovided.
/label ~"Quality" ~"QA" ~test
/label ~"Quality:test-gap" ~"Quality:EE test gaps"
/label ~"feature::addition" ~"feature::maintenance"