Quarantine flaky test
What does this MR do?
Quarantined because toggling the feature flag is flaky, and it's a reliable test. It's already fast quarantined
The best option to stop the flakiness is to update the test to handle the change behind the adherence_report_ui
feature flag, in a separate MR.
See #428979 (comment 1614182321)
E2E Test Failure issue(s)
Check-list
-
General code guidelines check-list -
Quarantine test check-list -
Follow the Quarantining Tests guide. -
Confirm the test has a quarantine:
tag with the specified quarantine type. -
Note if the test should be quarantined for a specific environment. -
(Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1).
-
-
Dequarantine test check-list -
Follow the Dequarantining Tests guide. -
Confirm the test consistently passes on the target GitLab environment(s).
-
-
To ensure a faster turnaround, ask in the #quality_maintainers
Slack channel for someone to review and merge the merge request, rather than assigning it directly.
Edited by Mark Lapierre