From 30bc74f20d89930611871b251233a8b75e24e16e Mon Sep 17 00:00:00 2001 From: "David H. Wilkins" Date: Tue, 27 Aug 2019 08:15:18 -0500 Subject: Broken Link to Test Design - previous link engineering/quality/guidelines/test-engineering/test-design is missing and apparently should be engineering/quality/test-engineering/#test-heuristics --- doc/development/testing_guide/best_practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 -- cgit v1.2.1