        |
|
 |
|
|||||||||||||||||
|
|||||||||||||||||
Test Plan
Objectives:
To verify that all functional requirements meet the specifications outlined
in the User Manual.
Scope:
The entire program. Method: There will be several phases used in testing
the program. The first phase is done by going down the list
of features, and testing to make sure all features work correctly.
This phase will be done manually by the Test Manager. The second phase
is a brute force test. It attempts to cover all possible uses of the program
by testing the limits of the different data fields, and abilities to store.
This phase will be done using testing software. The third phase will be
a random test. Features will be fiddled with in different odd orders,
to make sure there are no lingering side effects between procedures that
wouldn't normally be run together. This will be run by many of the group
members, in a wide effort to have as many views as possible working on
it.
Recording:
When a tester finds a bug, it is recorded into Teamatic. If the bug is
severe enough, it is also reported to the Integration Manager ASAP in
order to find the offending module.
Testing Criteria:
We are attempting to find accurate estimates of defects per lines of code.
Most industry figures are using C++ giving us an inaccurate estimate due
to the use of a much less error prone language, JAVA. When we do have
accurate data, we will make an estimate based on the lines of code in
our program. We will compare our number of defects to the estimation to
determine how many should be left.
System Test Procedure:
System Tests will be run to verify that the software product meets the
specified requirements as shown in the Test
Matrix. The system test cases are specified in the Detailed
Test Cases. Output for the test cases will be in the form of screen
captures and .properties or .java files. Tests will be run manually by
the test manager until all interface defects are fixed. After that, regression
tests will be automated using TASQ
Recorder. Please contact the test manager for the testing macros for
TASQ Recorder and theSystem test output..
Unit Test Procedure:
See Unit Test Procedure
03/12/01 Updated by John
02/11/01 Created by Cliff.
