Review Checklist for Acceptance Test Plan
This checklist is NOT intended as a starting point to write a document.|
It does NOT necessarily cover all aspects relevant for this type of document.
This checklist is intended only as an aid in checking a completed document.
- Are the entry conditions clearly and completely stated?
- What hardware is needed (stating relevant requirements on
processor speed, working memory, network facilities, hard disk space, ...)?
- What software is needed, including but not restricted to
the product source files (and that the version under test must have
been clearly tagged as such in the configuration management repository)?
- Which persons are needed to carry out what tasks (such as taking notes)?
- Is there an indication of how long it will typically take
to carry out the acceptance test?
When a full acceptance test takes more than two hours,
is it indicated which test procedures would constitute a reasonable
subset to carry out as initial acceptance test?
- Does each test procedure and each test case have a unique identifier?
- Are building and installing the product from sources included
as test cases?
- Does each test case have a backward tracing to
the specific user requirements that it covers?
Is a forward tracing table included (in an appendix):
for each user requirement, listing the test cases that cover it?
- Are input actions explicitly described,
so that they can be carried out without making further decisions?
Test cases should consist of a sequence of concrete and reproducible steps.
- Are pass/fail criteria clearly explained?
For instance, by providing concrete expected output,
or a way of checking actual output for conformation to the requirements.
©2008, Tom Verhoeff (TUE)
Feedback about this page is welcome