| |
|
|
Test Documents
Test Plan
The content of a test plan consist of the goals, extend and the focus of the test activities.
This document should help to clarify the What, Why and How to test a product.
In the following some keyword are listed which can be part of a test plan depending on the
project:
- Title
- Revision history of the document (author, date)
- Intention of the document, persons for which the document is written
- Relevant document list (guidelines, requirement specification, design documents, ...)
- Abbreviation list
- Test extend and limitations (test coverage, functionality, ...)
- Global assumptions and requirements for all tests
- Priorities and focus
- Personnel decisions
- Needed skills of the tester
- Description of the environment
- Setup and configuration of the test environment
- Description of special hard- and software
- Differences between test and real environment
- Requirements of test data
- Test tools and software (if necessary with version)
- Test tracking system
- Trouble report tracking and handling system
- Criteria for start and end of the test phase
- Showstopper criteria and handling process
- Decision about the test location
- Open questions
Test Specification
The purpose of a test specification is to give detailed information about the requirements,
the environment
and all the tests itself. So a consistent view and the reproducibility of the testing
should be guaranteed.
The content of a test specification is:
- Testing strategy
- Detailed environment description
- Global requirements
- Test case descriptions
Test Case Description
The description of the tests should be standardised and contain all necessary information to secure
a reproducible test execution.
- Unique id
- Short concise header
- Purpose
- Precondition
- Execution
- Expected result
- Valid for project/version
|
