Master Test List
The
Master Test List is the
test work product that lists all
system and launch test suites of test cases.
The typical objectives of a master test list are to:
- Enable stakeholders (e.g., clients and managers) to
understand how the application will be tested.
- Summarize all system test suites.
The typical benefits of a master test list Include:
- It enables the stakeholders to understand how the
application will be tested.
- It enables the management team can track the progress of
system and launch testing.
- It enables the testers to schedule system and launch
testing.
The typical contents of a master test list include:
The Master Test List documents the following information
about each kind of test:
- Test Suite Name
- Test Suite Objective
- Requirements Trace
- List of Test Cases
Any test suites or test cases that are reused can be listed
by reference. For example, functional test suites are often
reused during alpha and acceptance testing.
The typical stakeholders of a master test list include:
- Producer:
- Evaluator:
- Approvers:
- Maintainer:
- Users:
A master test list typically can be started if the following
preconditions hold:
The typical inputs to a master test list include:
- Work Products:
- Stakeholders:
- This is a living document that is developed incrementally
and iteratively in parallel with other work products.
- The information in the master test list is not included
in the project test plan because it is more volatile than the
information in the project test plan. This minimizes the
amount of iteration required by the project test plan.
- Not every kind of testing needs to be performed on every
project.
A master test list is typically constrained by the following
conventions:
-
Content and Format Standard
-
Template
-
Inspection Checklist