SOFTWARE MANAGEMENT PROGRAM
Software Testing Checklist
The following checklist is intended to provide system owners, project managers, configuration
managers, and other information system development and maintenance professionals with
guidance in identifying and planning testing activities. The checklist reflects recognized testing
activities to be performed throughout the information system (IS) life cycle.
Testing is generally characterized as validation that requirements have been met and that the
deliverables are at an acceptable level in accordance with existing standards during the initiation,
development, and operation phases of the IS life cycle.
The objectives of testing are summarized as:
Provide confidence that a product performs as expected without undesirable side
effects.
Note: There is a separate checklist for acceptance that includes acceptance testing.
Software Testing Checklist SEM Reference Comments
The test activities planned are documented. Chapter 4.0
Develop Project Test Plan
System and acceptance testing of the software are planned and Chapter 4.0
performed to demonstrate that the software satisfies its Develop Project Test Plan
requirements.
The testing necessary to validate that the project requirements Chapter 4.0
have been met has been established. Develop Project Test Plan
Obtain and review existing test material. Chapter 4.0
Develop Project Test Plan
The testing is adequate to verify the functionality of the software Chapter 4.0
product. Develop Project Test Plan
Resources, project team responsibilities, and management Chapter 4.0
activities needed to plan, develop, and implement the testing Develop Project Test Plan
activities that will occur throughout the lifecycle have been
identified.
The occurrence and timing of the test phases in the lifecycle and Chapter 4.0
the entrance and exit criteria for each test phase have been Develop Project Test Plan
identified.
The test products at each test phase have been specified. Chapter 4.0
Develop Project Test Plan
Mapping has occurred to identify which requirements are Chapter 4.0
verified in what test phase. Develop Project Test Plan
The criteria for evaluating the test results of each test phase have Chapter 4.0
been established. Develop Project Test Plan
The test environment (hardware, software, test tools, and data) Chapter 4.0
needed to conduct the tests has been determined. Develop Project Test Plan
A schedule for executing the test activities has been established. Chapter 4.0
Rev: 10/16/98 1
Software Testing Checklist SEM Reference Comments
Develop Project Test Plan
The test methodologies include the types of tests required, test Chapter 4.0
documents, test methods, and test data collection. Develop Project Test Plan
The Test Plan has been reviewed with the system owner prior to Chapter 4.0
conducting any tests. Develop Project Test Plan
Unit and integration tests with appropriate data have been Chapter 4.0
developed to exercise and validate all specified application Identify Test Methodologies
requirements, functions, and objectives.
Each type of test uses controlled computer generated or live data Chapter 4.0
as specified. Identify Test Methodologies
Discrepancies are identified, added to the problem report, and Chapter 4.0
problems resolved. Identify Test Methodologies
Retesting is required to verify that the problem solution Chapter 4.0
eliminates the problem and does not introduce new errors. Identify Test Methodologies
For each type of test conducted, the test results are compared Chapter 4.0
with the expected results. Identify Test Methodologies
The final test results are accompanied by a completed test Chapter 4.0
results/error log form. Identify Test Methodologies
The integration tests have been defined at each element level, Chapter 6.0
stating objectives, what is to be tested, and verified. Develop Integration Test Plan
All aspects of the formal interfaces that must undergo formal Chapter 6.0
integration testing have been defined. Develop Integration Test Plan
The test tools and software that must be developed to adequately Chapter 6.0
test the required functionality have been planned. Develop Integration Test Plan
A definition of, and the objectives for, each test case have been Chapter 6.0
provided. Develop System Test Plan
Rev: 10/16/98 2
Software Testing Checklist SEM Reference Comments
Detailed test scripts have been prepared for each Chapter 6.0
test case. Develop System Test Plan
The test scenario(s) including the step-by-step procedure, the Chapter 6.0
number of processing cycles to be tested or simulated, and the Develop System Test Plan
method and responsibility for feeding test data to the system
have been defined.
A test report, which documents test results and lists any Chapter 8.0
discrepancies, has been written at the completion of each level Conduct Integration Testing
of integration testing and placed in the project file.
A final test report was generated at the completion of integration Chapter 8.0
testing and placed in the project file. Conduct Integration Testing
All system test materials have been placed in the project file. Chapter 8.0
Conduct System Testing
A test report was generated at the completion of system testing Chapter 8.0
and placed in the project file. Conduct System Testing
A Stage Exit has been conducted for the integration and testing Chapter 8.0
stage. Conduct Software Integration and
Testing Stage Exit
Rev: 10/16/98 3
REFERENCES
The following resources can be referenced for additional information on software testing practices
and procedures. Note: This checklist is in compliance with Software Engineering Institute
guidance and most standards.
Software Engineering Methodology
Software Engineering Institute=s Software Capability Maturity Model (SEI CMM)
Software Product Engineering is a Key Process Area in Level 3 of the Model.
Institute of Electrical and Electronic Engineers (IEEE)
The IEEE Standard for Developing Software Life Cycle Processes
National Institute of Standards and Technology (NIST)
Organization for Standardization (ISO)
ISO 9001.
