E2E test: quarantine push mirror specs in CE
What does this MR do and why?
Quarantines qa/qa/specs/features/browser_ui/3_create/repository/push_mirroring_lfs_over_http_spec.rb and qa/qa/specs/features/browser_ui/3_create/repository/push_mirroring_over_http_spec.rb when running in CE only, as these tests consistently fail.
Failure issues:
The authentication method field is not being displayed in our CE e2e test pipelines (we use CE nightly build), possibly due to build differences, see #412611 (comment 1533085095). This cannot be reproduced in CE stable
#412611 (comment 1494669963)
Since this is a quarantine MR, no tests will be executed in the pipeline (https://gitlab.com/gitlab-org/gitlab/-/pipelines/1064564504)
I have created a test MR to demonstrate that the quarantining works correctly, as we haven't quarantined using this technique previously. In this MR qa/qa/specs/features/browser_ui/3_create/repository/push_mirroring_over_http_spec.rb is quarantined in !135685 (diffs)
Test quarantined in CE: https://gitlab-qa-allure-reports.s3.amazonaws.com/e2e-package-and-test-ce/jmc-quarantine-mirror-ce/1063586869/index.html#suites/e19fa0b0ebe2bdbf017f442661ceb0ee/97f0864261ed5dbc/
Test not quarantined in EE: https://gitlab-qa-allure-reports.s3.amazonaws.com/e2e-package-and-test/jmc-quarantine-mirror-ce/1063239060/index.html#suites/e19fa0b0ebe2bdbf017f442661ceb0ee/1833103caf16f337/
How to set up and validate locally
See pipelines of test MR.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.