From d594c7a9704dbf98dd78989f05ca0919bf5cf727 Mon Sep 17 00:00:00 2001 From: ddavison <ddavison@gitlab.com> Date: Fri, 21 Jun 2024 14:42:38 -0400 Subject: [PATCH] Rename qa-staging to e2e-run-staging --- doc/development/ai_features/duo_chat.md | 2 +- doc/development/feature_flags/index.md | 2 +- doc/development/testing_guide/end_to_end/index.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/development/ai_features/duo_chat.md b/doc/development/ai_features/duo_chat.md index f6c2a33758539430..fcca19a145b44de3 100644 --- a/doc/development/ai_features/duo_chat.md +++ b/doc/development/ai_features/duo_chat.md @@ -535,7 +535,7 @@ and, as an Admin, easily create licensed groups for testing. Duo Chat end-to-end tests run continuously against [Staging](https://staging.gitlab.com/users/sign_in) and [Production](https://gitlab.com/) GitLab environments. These tests run in scheduled pipelines and ensure the end-to-end user experiences are functioning correctly. -Results can be viewed in the `#qa-staging` and `#qa-production` Slack channels. The pipelines can be found below, access can be requested in `#test-platform`: +Results can be viewed in the `#e2e-run-staging` and `#qa-production` Slack channels. The pipelines can be found below, access can be requested in `#test-platform`: - [Staging-canary pipelines](https://ops.gitlab.net/gitlab-org/quality/staging-canary/-/pipelines) - [Staging pipelines](https://ops.gitlab.net/gitlab-org/quality/staging/-/pipelines) diff --git a/doc/development/feature_flags/index.md b/doc/development/feature_flags/index.md index 8efbc1a3105dd4f5..5534423f62616e0c 100644 --- a/doc/development/feature_flags/index.md +++ b/doc/development/feature_flags/index.md @@ -990,7 +990,7 @@ This means that end-to-end tests will run with feature flags in the default stat code, or with the feature flag in its current state on the GitLab instance under test, unless the test is written to enable/disable a feature flag explicitly. -When a feature flag is changed on Staging or on GitLab.com, a Slack message will be posted to the `#qa-staging` or `#qa-production` channels to inform +When a feature flag is changed on Staging or on GitLab.com, a Slack message will be posted to the `#e2e-run-staging` or `#qa-production` channels to inform the pipeline triage DRI so that they can more easily determine if any failures are related to a feature flag change. However, if you are working on a change you can help to avoid unexpected failures by [confirming that the end-to-end tests pass with a feature flag enabled.](../testing_guide/end_to_end/feature_flags.md#confirming-that-end-to-end-tests-pass-with-a-feature-flag-enabled) diff --git a/doc/development/testing_guide/end_to_end/index.md b/doc/development/testing_guide/end_to_end/index.md index 83931585e78cff07..0d7f728f9be633c2 100644 --- a/doc/development/testing_guide/end_to_end/index.md +++ b/doc/development/testing_guide/end_to_end/index.md @@ -30,7 +30,7 @@ You can find these pipelines at <https://gitlab.com/gitlab-org/gitlab/-/pipeline We run scheduled pipelines each night to test staging. You can find these pipelines at <https://gitlab.com/gitlab-org/quality/staging/pipelines> -(requires the Developer role). Results are reported in the `#qa-staging` Slack channel. +(requires the Developer role). Results are reported in the `#e2e-run-staging` Slack channel. ### Testing code in merge requests -- GitLab