diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-09-17 12:09:24 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-09-17 12:09:24 +0300 |
| commit | 877f19a2a14088de365f16ff4f95e5a8d96f8726 (patch) | |
| tree | 1eea037ce2a7f64565ada9d8060d3684eb22bc22 /doc/development/experiment_guide | |
| parent | 4f45a841a19e1d2ec32d3c0dd256978251c11061 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/experiment_guide')
| -rw-r--r-- | doc/development/experiment_guide/index.md | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/doc/development/experiment_guide/index.md b/doc/development/experiment_guide/index.md index ee871bc3ea7..4de272fec20 100644 --- a/doc/development/experiment_guide/index.md +++ b/doc/development/experiment_guide/index.md @@ -31,6 +31,10 @@ run) shouldn't impact GitLab availability. To avoid or identify issues, experiments are initially deployed to a small number of users. Regardless, experiments still need tests. +Experiments must have corresponding [frontend or feature tests](../testing_guide/index.md) to ensure they +exist in the application. These tests should help prevent the experiment code from +being removed before the [experiment cleanup process](https://about.gitlab.com/handbook/engineering/development/growth/experimentation/#experiment-cleanup-issue) starts. + If, as a reviewer or maintainer, you find code that would usually fail review but is acceptable for now, mention your concerns with a note that there's no need to change the code. The author can then add a comment to this piece of code |