Professional Documents
Culture Documents
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 organisation 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.
1. Preparation Of Tests
3. Completion of Testing
The Test Plan is the pivotal document around which all the software testing projects
revolve. It describes:
More details about this document are in the Test Plan overview article. If you wish to
see a more detailed version of a test plan then a UAT Plan Template which uses the
standard can be bought from this site.
The test design does not record the values to be entered for a test, but describes the
requirements for defining those values.
This document is very valuable, but is often missing on many projects. The reason is
that people start writing test cases before they have decided what they are going to test.
The exact input values that will be input and the values of any standing data that is
required,
The exact output values and changes of value of the internal system state that are
expected,
And any special steps for setting up the tests.
Defining the expected values is very important, for only by doing this can discrepancies
be spotted. However in some projects they are not defined which results in a very poor
quality set of test cases.
A feature from the Test Design may be tested in more than one Test Case, and a Test
Case may test more than one feature. The aim is for a set of test cases to test each
feature from the Test Design at least once. Taking the Billing project example all three
requirements could be tested using two test cases:
The first test case could test both that a normal bill is produced and that a volume
discount is properly calculated.
A second test case could check that a final bill is produced and a volume discount
is calculated.
The Test Log records the details of what Test Cases have been run, the order of their
running, and the results of the test. The results are either the test passed, meaning that
the actual and expected results were identical, or it failed and that there was a
discrepancy. If there is a discrepancy than one or more Test Incident Reports are raised
or updated, and their identities recorded on the Test Log.
The Test Log is important as it allows progress of the testing to be checked, as well as
providing valuable information for finding out what caused an incident. If an incident is a
coding fault, the fault may have occurred not in the Test Case that failed but in one that
was run previously. Thus the sequence of the tests enables the fault to be found.
The Test Summary brings together all pertinent information about the testing, including
an assessment about how well the testing has been done, the number of incidents
raised and outstanding, and crucially an assessment about the quality of the system.
Also recorded for use in future project planning is details of what was done, and how
long it took.
This document is important in deciding whether the quality of the system is good
enough to allow it to proceed to another stage.