SOFTWARE TEST PLAN & REPORT
for the
MIT 16.070 Final Project
[Day Month Year]
Prepared for:
Massachusetts Institute of Technology
Department of Aeronautics and Astronautics
Spring 2002
Prepared by:
[Name]
[Campus Contact Information]
SOFTWARE TEST PLAN & REPORT
for the
MIT 16.070 Final Project
Spring 2001
Approved by:
Teaching Assistant
Date
Professor
Date
[Other]
Date
ii
TABLE OF CONTENTS
1.
EXECUTIVE SUMMARY ...................................................................................................1
1.1
1.2
2.
SOFTWARE TEST ENVIRONMENT ..............................................................................1
2.1
2.2
2.3
3.
Serial I/O Test(s) ..........................................................................................................5
Thrust / Rotation Controller Test(s) .........................................................................5
Simulator Test(s) ..........................................................................................................5
Hardware Tests ............................................................................................................5
Graphics Package Tests ..............................................................................................5
System Test(s)...............................................................................................................5
TEST RESULTS ....................................................................................................................6
4.1
4.2
4.3
5.
Software Items Under Test ........................................................................................1
Components in the Software Test Environment ...................................................1
Software Test Configurations ...................................................................................2
TEST IDENTIFICATION – PLANNED TESTS .............................................................5
3.1
3.2
3.3
3.4
3.5
3.6
4.
System Overview .........................................................................................................1
Document Overview ...................................................................................................1
Overall Assessment of the Software Tested...........................................................6
Recommended Improvements ..................................................................................6
Detailed Test Results ..................................................................................................6
4.3.1
Serial I/O Test(s) ...........................................................................................6
4.3.2
Thrust Controller Test(s) ..............................................................................6
4.3.3
Simulator Test(s) ............................................................................................6
4.3.4
Hardware Test(s) ...........................................................................................6
4.3.5
Graphics Package Test(s) ..............................................................................6
4.3.6
System Test(s).................................................................................................7
NOTES ....................................................................................................................................7
iii
1.
1.1
EXECUTIVE SUMMARY
System Overview
This paragraph shall briefly state the purpose of the system and the software to which this
document applies. It shall describe the general nature of the system and software; summarize the
history of system development, operation, and maintenance. Take a portion of the project writeup
and include it here for clarification of the requirements.
1.2
Document Overview
This paragraph shall summarize the contents of this document. It shall summarize the key
tests run and the success/failure of the tests. It shall also include an overall assessment of the MIT
16.070 project software. One should be able to read this section and know what to expect in the rest
of the document. Use this paragraph to describe (at a high level) what happened in your testing.
2.
SOFTWARE TEST ENVIRONMENT
2.1
Software Items Under Test
This paragraph shall identify any software by name, number and version, as applicable
that is being tested as part of this plan. (This is the student handyboard software itself).
2.2
Components in the Software Test Environment
This paragraph shall identify by name, number, and version, as applicable, the support
software items (e.g., operating systems, compilers, communications software, related applications
software, databases, input files, code auditors, dynamic path analyzers, test drivers, preprocessors,
test data generators, test control software, other special test software, post-processors) necessary to
perform the planned testing activities on the software identified in paragraph 2.1. (This includes
the simulation software that was written for the workstation and any software that was written in
support of test harnesses, version of the handyboard OS, Visual C version on your PC, etc.)
1
2.3 Software Test Configurations
Configuration 1: Test Harness connected to Student Controller
Test Value
to Controller
Expected
Command
64
2
1
10
1
28
128
File driven
Test
Harness
64, 1, 1, 128
… 2, 10, 28
Serial I/O
Configuration 2: Stand-alone Workstation Simulation
x position, x velocity
y position, y velocity
Initial heading Θ
Workstation
Simulation
Thrust commands
Rotate commands
Next vehicle
state
2
Student
HB Controller
Configuration 3: Test Harness designed to test Simulator serial I/O upgrade
Velocity
IR status
HB
Test
Harness
Workstation
Simulation
Thrust commands
Rotate commands
Next vehicle
state
Configuration 4: Student Handyboard communicating over serial I/O with workstation
Student
HB
Controller
Velocity
IR status
Workstation
Simulation
Thrust commands
Rotate commands
3
Next
vehicle state
Configuration 5: Student Handyboard controlling Vehicle
Student
HB
Controller
Velocity
IR status
Vehicle
(on board
Handyboard)
Thrust commands
Rotate commands
4
3.
TEST IDENTIFICATION – PLANNED TESTS
3.1
Serial I/O Test(s)
This paragraph shall describe the tests to be run to confirm operation of the serial I/O
portion of the MIT16.070 project. It shall include a description of any test code that will support
the test (but is not part of the actual project software).
Serial I/O testing occurs using
configuration 1 (Part A of the project). Serial I/O testing may also be necessary in configuration 3.
3.2
Thrust / Rotation Controller Test(s)
This paragraph shall describe the tests to be run to confirm operation of the thrust /
rotation controller portion of the MIT16.070 project. It shall include a description of any test code
that will support the test (but is not part of the actual project software). This testing verifies the
handyboard controller behavior vs. the expected behavior in the state transition diagram. Testing
occurs using configuration 1.
3.3
Simulator Test(s)
This paragraph shall describe the tests to be run to confirm operation of the simulation
portion of the MIT16.070 project. Simulator testing occurs using configuration 2 (standalone
verification). Simulator serial I/O testing may also be necessary in configuration 3. Include a
description of any test code that will support the test (but is not part of the actual project software).
You may write up this testing here, or in section 3.1(Serial I/O).
3.4
Hardware Tests
This paragraph shall describe the tests to be run to confirm operation of the hardware
portions of the MIT16.070 project. It shall include a description of the IR characterization tests
(extra credit), the Vehicle characterization tests (extra credit) and the suspended vehicle tests
(required).
3.5
Graphics Package Tests
This paragraph shall describe the tests to be run to confirm the interface to the graphics
package provided to compliment the simulator. This testing occurs in configuration 2.
3.6
System Test(s)
This paragraph shall describe the tests to be run to confirm operation of the integrated
system for the MIT16.070 project.
5
4.
TEST RESULTS
4.1
Overall Assessment of the Software Tested
This paragraph shall:
4.2
(a)
Provide an overall assessment of the software as demonstrated by the test results in
this report
(b)
Identify any remaining deficiencies, limitations, or constraints that were detected by
the testing performed.
Recommended Improvements
This paragraph shall provide any recommended improvements in the design, operation, or
testing of the software tested. A discussion of each recommendation and its impact on the software
may be provided. If no recommended improvements are provided, this paragraph shall state
"None."
4.3
Detailed Test Results
4.3.1
Serial I/O Test(s)
This paragraph shall describe the results of each test including any problems encountered
during the testing of the serial I/O portion of the MIT16.070 project.
4.3.2
Thrust Controller Test(s)
This paragraph shall describe the results of each test including any problems encountered
during the testing of the thrust controller / state transition diagram portion of the MIT16.070
project.
4.3.3
Simulator Test(s)
This paragraph shall describe the results of each test including any problems encountered
during the testing of the simulation portion of the MIT16.070 project.
4.3.4
Hardware Test(s)
This paragraph shall describe the results of each test including any problems encountered
during the testing hardware portion the MIT16.070 project.
4.3.5
Graphics Package Test(s)
6
This paragraph shall describe the results of each test including any problems encountered
during the testing of the graphics package interface portion of the MIT16.070 project.
4.3.6
System Test(s)
This paragraph shall describe the results of each test including any problems encountered
during the testing of the integrated MIT16.070 project.
5.
NOTES
This section shall contain any general information that aids in understanding this
document (e.g., background information, glossary, rationale). This section shall include an
alphabetical listing of all acronyms, abbreviations, and their meanings as used in this document and
a list of any terms and definitions needed to understand this document.
7