Check done by Document under review

Role Version
Project Review date

Checklist Sanity Check: Test ware

Conclusion
Conclusion Y / N
The testware is described accurately enough and/or works well enough
for reuse

When conclusion is negative:

High-level errors that were recorded during the sanity check are displayed below. For each error,
indicate the risks for the test design and the measures needed to rectify them.

Error Risk Measure

Result
Name Y/N N.A. Solutions
The functionality that is to be tested and the
processes and their coherence are sufficiently
described
The functionality and the processes and their
coherence concur with the anticipated goal
All of the relevant quality attributes have been
sufficiently taken care of
The outcome of the risk analysis is traceable in the
test design
Test results from the last time the testware was
used are available and provide insight into the
quality of the tests
Errors that were found after last time the testware
was used are available and indicate on what points
the coverage of the testware is insufficient

Logical tests
Name Y/N N.A. Solutions
The test basis on which the logical test is based is
clearly specified
The logical test design is up to date, there are no
major outstanding issues in the design specified in
the test base
The structure of the test design is clear
Checklist Sanity Check: Test ware
TestGoal template Page 1/3
 Check done by Document under review
Role Version
Project Review date

Logical tests can be traced back to related

specification elements so changes in the test base
can efficiently implemented
Logical tests can be traced back to the related risk
category in the TRA so changes in the TRA can be
efficiently implemented
Logical tests are set up on the basis of test
techniques
Where needed, test techniques are applied correctly
and completely
Choices that have been made in the logical test
design have been clearly indicated (for example,
deviations from the technique)

Physical test
Name Y/N N.A. Solutions
The test base on which the physical test case is
based is clearly specified
The physical test design is up to date, there are no
major outstanding issues in the design specified in
the test base
The structure of the test design is clear
The physical tests can be traced back to the related
specification elements so changes in the test base
can be efficiently implemented
Physical tests can be traced back to the related risk
category in the TRA so changes in the TRA can be
efficiently implemented
Physical tests can be traced back to the related
logical test design so changes in the logical test
design can efficiently implemented
The test base on which the physical test case is
based is clearly specified

Test cases
Name Y/N N.A. Solutions
Test cases have a unique ID
Test cases contain all the required fields
Test cases are detailed, it is clear what the purpose
of the test is and when the test is successful
Test cases clearly describe which test actions will
be executed
Test cases describe the input data that is used and
the expected outcome

Checklist Sanity Check: Test ware

TestGoal template Page 2/3
 Check done by Document under review
Role Version
Project Review date

Test tooling
Name Y/N N.A. Solutions
The test base on which the tooling is based is
clearly indicated
The tooling is up to date, there are no major
outstanding issues in the design specified in the test
base
There are errors in the tooling and they have a clear
status. It can be estimated which bug fixes/ changes
will have to be performed on the tools
Documentation for the tooling is available, so
changes can be efficiently implemented
The infrastructure is such that the tooling can be
tested before the actual test run starts

Checklist Sanity Check: Test ware

TestGoal template Page 3/3