Skip to content

[Feature flag] Rollout quality_test_cases

What

Remove the :quality_test_cases feature flag.

Owners

  • Team: Plan
  • Most appropriate slack channel to reach out to: #g_plan
  • Best individual to reach out to: @felipe_artur

Expectations

Test cases tab will be shown on left sidebar under CI/CD.

What are we expecting to happen?

Users will be able to create new test cases.

What might happen if this goes wrong?

Don't expect any serious problems on other parts of the application.

Since test cases are extensible issues maybe new test cases can be displayed on unexpected places.

What can we monitor to detect problems with this?

https://sentry.gitlab.net/gitlab/gitlabcom/

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

  • gitlab-org/customers-gitlab-com
  • gitlab-org/quality/testcases
  • gitlab-org/requiremeents-mgmt

Roll Out Steps

  • Enable on staging
  • Test on staging
  • Ensure that documentation has been updated
  • Enable on GitLab.com for individual groups/projects listed above and verify behaviour
  • Coordinate a time to enable the flag with #production and #g_delivery on slack.
  • Announce on the issue an estimated time this will be enabled on GitLab.com
  • Enable on GitLab.com by running chatops command in #production
  • Cross post chatops slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
  • Announce on the issue that the flag has been enabled
  • Remove feature flag and add changelog entry
  • After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel
Edited by Felipe Cardozo