Test Strategy

„If you don’t know, where you are, every path is equally good“
(Chinese saying)

From the requirements for a software system, all theoretically possible test cases can be derived automatically to verify their correctness within the test. But the combinatorical explosion does not allow the execution of the huge amount of test cases within a reasonable timeframe.

We will develop an ideal strategy to perform

the most important test cases
within the existing timeframe
in the necessary depth

Approach

On the basis of the software specifications (test basis) we determine a list of needed quality characteristics and create a requirement catalog.

Within a workshop we value the relevance of each quality characteristic together. In the same workshop we will also define the test objects and their risk valuation, do an examination identify which standard test approach is actually used in the company and analyze the available human and technical resource.

On the basis of this information we design a test strategy in which every test object and quality characteristic will be described and in which test methods, test phases and test depth will be applied. With the risk evaluation a formula-based assignment of the testing efforts to the single test objects will be done. The definition of measurable test ending criteria, whose fulfilment means the end of test, as well as the test break off criteria complete the strategy.

In a presentation we illustrate our proposal and agree on it together in a concluding workshop.

Results

Requirements catalog (tabular overview of all requirements)
Agreed test strategy including test end criteria and test break off criteria

Benefit

Taking account of all quality characteristics through adequate testing methods
Optimal assignment of human and technical resources
Achievement of the best-possible test depth through a risk-based approach
Clearly structured test strategy which can always be adapted to changing conditions in order to execute the most important test cases.
Measurable test goals and therefore a clear statement when a test is terminated respectively what the status of testing currently is.

Prerequisites

Test basis (= project brief, business proposal and it concept) are available.

Contact About Imprint