diff options
author | Luke Duncalfe <lduncalfe@gitlab.com> | 2019-05-17 21:36:52 +0300 |
---|---|---|
committer | Achilleas Pipinellis <axil@gitlab.com> | 2019-05-17 21:36:52 +0300 |
commit | db7dabea674d30c170ab22b43efd86a5d91ccdfc (patch) | |
tree | 57487e36bc39a5d0f0d120d772ef2b48aad19fe5 /doc/development/feature_flags.md | |
parent | 8739c0095c999e8d2e49a7f96aef7ef6ec73ebe6 (diff) |
Link to testing guide for feature flag spec info
In order for there to be a single source of truth.
Diffstat (limited to 'doc/development/feature_flags.md')
-rw-r--r-- | doc/development/feature_flags.md | 8 |
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) |