Next: Code
instructions
Previous: Detailed
design document instructions
Up: all milestones
CMPS115, Milestone 4
Test Plan and Unit Test Report Instructions
Assignment due in lab: Develop a
test plan and unit test reports (TPUTR) for
your game. Please remember to include the time recording logs.
1) Test Plan: (10% of the TPUTR points)
A test plan outlines the kinds of testing you will do of your system,
who is responsible for the testing, and the work products that will be
submitted when testing is complete. For your project, you are to cover 6
items in your test plan.
- Test unit specification.
Here you state that
you will be doing two different kinds of testing of your system: system
testing of the functionality according to the functions
specified in your RSD and 4, 5, or 6 structural
tests of units. You need to define the extent of these 4, 5, or 6 units.
For example, if each of your group members is going to unit test an
entire class' member functions, then you state that fact here. If
instead, only a single member function is to be unit tested by each
group member, state that fact. List the units to be tested by each
person. DO NOT PERFORM THE TESTING NOW.
- Features to be tested.
Generally, in the test plan you detail the different features to be
tested. This can include functionality, performance, design constraints,
and attributes. For this class, you are only required to test
functionality. Any other kind of feature testing can be done. If you
care to include other kinds, please indicate it in this section.
- Approach for testing.
There are many different testing approaches. You are only required to
do functional testing at the system level and 100% branch coverage (a
form of structural testing) at the unit level. For this item, please indicate
the approach: functional for system and 100% branch
coverage (structural) for the units.
- Test deliverables.
Define your deliverables for
testing to be the detailed results of the testing, including test case
specifications (mapped to cover all of the functions from section 3.2 of
RSD), and a test log which gives details about the execution of the
tests. Include a definition of your deliverables for the unit tests.
The deliverable for a unit test is the unit test report. See below for
the contents of the unit test report.
- Schedule.
Define your schedule to fit in with the milestones that I've given you.
- Personnel allocation.
State the personnel allocation for the unit and system
testing. The personnel allocation for your system testing will probably
be your entire group, but may not be.
2) Unit Test Report (one per group member - a different unit per group
member). Prepare the deliverables for the unit testing of the 4, 5, or 6 units
that you specified in your test plan (ie. the unit test report contains
the test case specifications - input, expected output, branches covered
for each test case; do a structural test (using a written and implemented
driver and stubs if necessary), a test log
(the actual output for each of the test cases), and
summarized error report). Include the code of any scaffolding needed (test
drivers and stubs). Include the code for the unit under test. Note that a
control flow graph of the unit is suggested. This is worth 80% of the
TPUTR points.
3) Group time log. This is worth 5% of the TPUTR points.
4) Meeting minutes. This is worth 5% of the TPUTR points.
Next: CODE instructions
Up: all milestones
Acknowledgements: I would like to gratefully acknowledge Linda Werner, the author of this assignment.
Jim Whitehead
Last modified: Jan. 16, 2001