Identify staging-only tests and refactor for pipeline reordering
Description
Some E2E tests target the staging
environment. These should be updated to also target staging-canary
with the pipeline reorder so these tests are executed before new code is available to customers.
Tests
-
qa/specs/features/api/5_package/container_registry_spec.rb -
qa/specs/features/browser_ui/1_manage/login/maintain_log_in_mixed_env_spec.rb -
qa/specs/features/browser_ui/3_create/repository/push_to_canary_gitaly_spec.rb -
qa/specs/features/browser_ui/5_package/container_registry/container_registry_spec.rb -
qa/specs/features/browser_ui/7_configure/auto_devops/auto_devops_templates_spec.rb -
qa/specs/features/browser_ui/7_configure/auto_devops/create_project_with_auto_devops_spec.rb -
qa/specs/features/ee/api/7_configure/kubernetes/kubernetes_agent_spec.rb -
qa/specs/features/ee/browser_ui/13_secure/license_compliance_spec.rb -
qa/specs/features/ee/browser_ui/1_manage/group/prevent_forking_outside_group_spec.rb -
qa/specs/features/ee/browser_ui/1_manage/project/project_templates_spec.rb -
qa/specs/features/ee/browser_ui/3_create/repository/pull_mirroring_over_ssh_with_key_spec.rb -
qa/specs/features/ee/browser_ui/4_verify/pipeline_for_project_mirror_github_spec.rb
There are six additional specs in fulfillment that may need to be targeted in the future, but left out at the moment due to Zuora integration
Edited by Zeff Morgan