Add merge trains transient bug test
What does this MR do?
Adds a new e2e test for merge trains transient bugs: gitlab-org/quality/testcases#1608
It has a new transient
tag, which is excluded by default and has to be specified (--tag transient
) to run the test.
New jobs were added to run the test in only the nightly pipeline: https://gitlab.com/gitlab-org/quality/nightly/-/merge_requests/77
See https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/759
This is currently just a copy of an existing test, with a minor change to remove one retry. It's basically just a placeholder until I get more clarity on the regression it's intended to test for.
Got some clarity now. Notes in https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/759#note_489306705.
This test isn't for a specific bug because the original issue turned out to be working as intended. However, this does form the base for more specific tests that I plan to add as noted in https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/759#note_489306705
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry
-
Documentation (if required) -
Code review guidelines - [-] Merge request performance guidelines
-
Style guides - [-] Database guides
- [-] Separation of EE specific content
Ooops, I forgot to use the template...
-
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. -
Ensure that no transient bugs are hidden accidentally due to the usage of waits
andreloads
. -
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