From 2724fbe2ce8afe7b11876601720bd29c6ffef777 Mon Sep 17 00:00:00 2001 From: Brian Hoffmann Date: Wed, 2 Jun 2021 14:57:08 +0200 Subject: [PATCH] Fix ISTQB glossary link --- radar/2017-03-01/explicit-test-strategy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/radar/2017-03-01/explicit-test-strategy.md b/radar/2017-03-01/explicit-test-strategy.md index 2ba695b..e86b244 100644 --- a/radar/2017-03-01/explicit-test-strategy.md +++ b/radar/2017-03-01/explicit-test-strategy.md @@ -4,7 +4,7 @@ ring: assess quadrant: methods-and-patterns --- -According to the [ISTQB Glossar](http://glossar.german-testing-board.info/#teststrategie)- a **Test Strategy** is an abstract specification that comprises the designated test levels (unit, integration, system and acceptance tests) and the implementation of each level for a whole organization or for an application. This test strategy can be applicable to one or more projects. +According to the [ISTQB Glossar](https://glossary.istqb.org/)- a **Test Strategy** is an abstract specification that comprises the designated test levels (unit, integration, system and acceptance tests) and the implementation of each level for a whole organization or for an application. This test strategy can be applicable to one or more projects. At AOE, we established an explicit test strategy for many of our projects. The coordination of the test levels improves the effectivity of test runs and helps to avoid testing gaps, double inspection and overhead. Every test level has a different focus. Tests that are executed on one level don't have to be implemented on others.