summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLuke Duncalfe <lduncalfe@eml.cc>2019-04-11 17:04:01 +1200
committerLuke Duncalfe <lduncalfe@eml.cc>2019-04-11 17:17:47 +1200
commit1186d481eacbe8330a438f458a0b669d797c6d86 (patch)
treeeccc079b31bb6af86725cfccf737db6d381fdaf0
parent9b7ddd323d6910dbc3ecca54d292fda7a85cfa9d (diff)
downloadgitlab-ce-add-testing-feature-flags-docs.tar.gz
Link to testing guide for feature flag spec infoadd-testing-feature-flags-docs
In order for there to be a single source of truth.
-rw-r--r--doc/development/feature_flags.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/development/feature_flags.md b/doc/development/feature_flags.md
index 3271f9a7fb3..82b09cc0224 100644
--- a/doc/development/feature_flags.md
+++ b/doc/development/feature_flags.md
@@ -108,11 +108,11 @@ so we make sure behavior under feature flag doesn't go untested in some non-spec
contexts.
Whenever a feature flag is present, make sure to test _both_ states of the
-feature flag. You can stub a feature flag as follows:
+feature flag.
-```ruby
-stub_feature_flags(my_feature_flag: false)
-```
+See the
+[testing guide](testing_guide/best_practices.html#feature-flags-in-tests)
+for information and examples on how to stub feature flags in tests.
## Enabling a feature flag (in development)