summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2019-08-30 01:25:30 +0000
committerEvan Read <eread@gitlab.com>2019-08-30 01:25:30 +0000
commit13627ca919ae263cc78d37fbfec78dd4e0af19a4 (patch)
tree208a9a79f52855d379482d662d85da5d6c6ff722
parent25341f5807545edc7fb97f9acdbfd9b23258e3c5 (diff)
parent30bc74f20d89930611871b251233a8b75e24e16e (diff)
downloadgitlab-ce-13627ca919ae263cc78d37fbfec78dd4e0af19a4.tar.gz
Merge branch 'fix-test-design-link' into 'master'
Broken Link to Test Design See merge request gitlab-org/gitlab-ce!32279
-rw-r--r--doc/development/testing_guide/best_practices.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/development/testing_guide/best_practices.md b/doc/development/testing_guide/best_practices.md
index f30a83a4c71..0f982c3a48b 100644
--- a/doc/development/testing_guide/best_practices.md
+++ b/doc/development/testing_guide/best_practices.md
@@ -13,7 +13,7 @@ a level that is difficult to manage.
Test heuristics can help solve this problem. They concisely address many of the common ways bugs
manifest themselves within our code. When designing our tests, take time to review known test heuristics to inform
our test design. We can find some helpful heuristics documented in the Handbook in the
-[Test Design](https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/test-design/) section.
+[Test Engineering](https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-heuristics) section.
## Test speed