Over the years a number of types of document have been invented to allow for the control of testing.They apply to software testing of all kinds from component testing through to release testing.Every organization develops these documents themselves and gives them different names,and in some cases confuses their purpose.To provide a common set of standardised documents the IEEE developed the 829 standard for software test documentation for any type of software testing,including user acceptance Testing.
This article outlines each of the types of document in this standard and describes how they work together.
The Types of Document
There are eight document types in the IEEE 829 standard, which can be used in three distinct phases of software testing:
1.Preparation of Tests
* Test plan: Plan how the testing will proceed
* Test Design Specification : Decide what needs to be tested
* Test Case specification: Create the tests to be run
* Test procedure: Describe how the tests are run
* Test item Transmittal Report: Specify the items released for
testing.
2. Running the Tests
* Test log: Record the details of tests in time order
* Test incident report: Record details of tests in time order
3. Completion of Testing
* Test summary Report: Summarise and evaluate tests.
These are eight document types which can be used in three distinct phasesof software testing.If anybody wants elabrated details of this IEEE 829 Document can send your comments and it will be posted as soon as possible.
