Test concept

Project name

Classification	Select an element
Status	Select an element
Program name
Project number
Project manager	Project manager
Version	0.1
Date	Click here to enter a date
Project sponsor	Project sponsor
Author(s)
Distribution

List of changes

Version	Date	Change	Author
0.1

Table 1:	Change control

Description

The test concept describes the test objectives, test objects, test types, test infrastructure and test organization. It also includes test planning and test case descriptions. A detailed test case description is created for each test case. This constitutes the test specifications. Test planning determines the logical and chronological structure of the tests. The test concept forms the basis on which the test organization and test infrastructure are provided and the tests are carried out. It is always updated in the case of new findings.

Test objectives

Overall measurable test objectives across all test cases:

No.	Description	Measurement variable	Priority*
1	Interface test successful	Exchange of data correct	M
2	System architecture meets the requirements of xy
3	Program abc functional
* Priority: M = mandatory / 1 = high, 2 = medium, 3 = low

Table 2:	Overarching test objectives

Test strategy and test levels

Efficient testing requires a well thought-out (and possibly agile) test strategy:

With which test strategy can the development be accompanied and supplemented in order to achieve the specified quality?

Which test levels are there/from which test level should testing begin?

How can overlaps between different test levels be avoided (prevention of redundancies)?

How can deficits in the available test environment be circumvented/overcome?

etc.

Test objects

No.	Item	Description
1
2

Table 3:	Test objects

Test types

No.	Test type	Description
1
2

Table 4:	Test types

Test coverage

Overview of test cases

No.	Test object	Test case
1
2

Table 5:	Test coverage

Assessment of test objectives and test coverage

Test framework

Test prerequisites

Tester, previous knowledge

Defect classification

The defects found, or the requirements not fulfilled (expectations), are classified from 1 to 4. Category 0 is used only if a faultless outcome is to be shown separately:

No.	Defect category	Description
0	Flawless	Flawless and in line with requirements
1	Insignificant defect	Use possible, proven usability, no defects should occur
2	Minor defect	Use possible, usability is only slightly impaired
3	Major defect	Use still possible, usability is greatly reduced
4	Critical defect	Unusable Key functionality missing Operation is not acceptable (e.g. security reasons)

Table 6:	Defect categories

The classification reflects the severity of the consequences and the time and effort required to remedy the defects that can be identified. The allocation of the defects found to a defect category also roughly determines the order of priority for remedying the defects.

In the case of defect category 1 to 3, the system/product can be accepted with reservations. However, measures to remedy the defects must be defined. A supplementary review is mandatory.

If, instead, category 4 defects are found, the system/product cannot be accepted and the provider must take immediate measures to remedy these defects. The provider must also arrange for another acceptance procedure.

Starting and abandonment conditions

Prerequisites for start of test

Test environment

Description and organization of the required (practical) test environment(s).

Test infrastructure

Test system

Test data

Test tools

Software for test management

List of reports

Test organization

Test case descriptions

ID/designation	T-001	Reference to requirement & acceptance criterion	nn e.g. the quality requirements in the system requirements outcome
Description
Test prerequisites
Test steps
Expected outcome

Table 7:	Test case description

Test plan

No.	Activity	Resp.	Collaboration	Deadline
1
2
3

Table 8:	Test plan

Abbreviations and glossary

Abbreviation/specialist term	Explanation
HERMES	Methodology for projects and programs HERMES 5 is an eCH standard

Table 9:	Abbreviations and glossary

Contents

List of changes	1

Description	1

1	Test objectives	2

2	Test strategy and test levels	2

3	Test objects	2

4	Test types	2

5	Test coverage	3

5.1	Overview of test cases	3

5.2	Assessment of test objectives and test coverage	3

6	Test framework	3

6.1	Test prerequisites	3

6.2	Defect classification	3

6.3	Starting and abandonment conditions	4

7	Test environment	4

8	Test infrastructure	4

8.1	Test system	4

8.2	Test data	4

8.3	Test tools	4

9	Test organization	4

10	Test case descriptions	4

11	Test plan	5

Abbreviations and glossary	6

Contents	7

Tables	8

Tables

Table 1:	Change control	1

Table 2:	Overarching test objectives	2

Table 3:	Test objects	2

Table 4:	Test types	2

Table 5:	Test coverage	3

Table 6:	Defect categories	3

Table 7:	Test case description	4

Table 8:	Test plan	5

Table 9:	Abbreviations and glossary	6