Software Test Plan(测试计划)

1.1 Software Test Plan (STP)

1.2 Table of Contents
1.0 Introduction
o
1.1 Purpose of Document
o
1.2 Scope of Product
o
1.3 Definitions, Acronyms, and Abbreviations
o
1.4 References
o
1.5 Overview of Rest of Document
?
2.0 Test Items
o
2.1 Requirements to be tested
o
2.2 Requirements not tested
?
3.0 Approach
?
4.0 Test Cases
o
Test Case 1
?

1.0

I
NTRODUCTION

1.1 Purpose of Document
The purpose of the Software Test Plan (STP) is to test the functionality and make sure
that the requirements stated in the Software Requirement Specification are fulfilled.
These requirements are listed under Section 3.1 of Software Requirement Specification.
1.2 Scope
The Comment Counter is a freeware 32-bit Windows 98 application that allows its users
to derive various statistics from an analysis of their source code. Our product will parse
any source code file or files that the user specifies (for the standard version, this will be
any C or C++ files, and for the professional version, this will be any Java, VB, or HTML
files, in addition to the C and C++ files), and will display the number of bytes of
comments that the file or files contain, the total number of bytes in the file or files, and
the percentage of bytes of comments out of the total number of bytes in the file or files.
The Comment Counter will display a real-time running count of these statistics as the file
or files are being read, and it will allow the user to create an HTML-based report based
on these statistics.
These are the individual team members responsibility:
?
?
?
?
?
?
?
?
?
Handy Firmansjah - Project Lead Engineer, Product Information Engineer, Tester.
Eric Simons - C++ Developer, Product Information Engineer.
Tony Chen - C++ Developer, Webmaster.
Ryan Chen - Build Release Engineer, Test Engineer.
Julie Tran - Test Engineer, Project Administrator.
Kamlesh Patel - Test Engineer.
Jessica Zhang - VB Developer.
Ting-Wei Chou - C++ Developer.
Jennifer Le - C++ Developer, VB Developer.
1.3 Definitions, Acronyms, and Abbreviations
DLL
Dynamic Link Library
GUI
Graphical User Interface
HTML
Hypertext Markup Language
LAN
Local Area Network
MB
Megabytes
OS
Operating System
RAM

Random Access Memory
SDD
Software Design Document
SRS
Software Requirements Specification
STP
Software Test Plan.
URL
Uniform Resource Locator
1.4 References
Software Requirements Specifications
http:~
?
Weekly Builds http:~
?
1.5 Overview of Rest of Document
This section will be an overview of what can be found within the other section of the STP.
?
?
?
?
?
?
Section 2.0: Test items This section lists test cases that we will and will not be
doing corresponding to the SRS.
Section 3.0: Approach This section describe the general testing approach that will
be taken by the Integration Test Engineers.
Section 4.0: Test Cases This section describes in detail how each test is going to
be carried out.
Section 5.0: Test Log This section logs the outline of the result of the test cases.
Section 6.0: Test Results This section shows how many test passes out of the total
number of test.
Section 7.0: Traceability Matrix This Section shows the mapping of each
requirement listed in section 3 of the SRS to its corresponding Test Case in the
STP that will demonstrate the requirement.

3.0

A
PPROACH

This section describes the general testing approach that will be used to test the major set
of features of the product. Software testing shall be performed throughout the
development phases starting with unit testing, integration, incremental testing, and
finishing with system qualification testing. The software shall be tested on the system
requirements.
3.1 Team Roles
Following table provides a summary of major test activities as a Member's roles
and Member's responsibilities.
Member's Roles Member's Responsibilities
Check documents for process compliance
Review test procedure
Project Lead
Monitor testing schedule and status
Perform Quality Assurance
Schedule
Project Administration
Test control
Conduct informal unit testing
Maintain informal development folder which includes unit and incremental
Programming Team test results
Support integration and system testing
Dispose Project Problem Reports (PPRs)
Develop Software Test Plan (STP)
Prepare test cases
Software Test Team Perform incremental testing and final qualification testing
Write up test reports
Submit Project Problem Reports (PPRs)
Project Builds
Project Builder Software Build Release Notes
Maintain software configuration control
3.2 Project Scheduling
Testing scheduling and status reporting are performed by the Project Lead and project
Administrator to monitor progress towards meeting product testing schedules and release
date, as well as to identify any project scheduling risks. Each build will be tested before
next subsequent build date. Software testing schedules will coincide with module
development and release schedules.
3.3 Quality Assurance
Project lead will be responsible for quality Assurance(QA) related activities. It includes
checking of test documentation for process compilance, reviewing test procedures, and
determining when the product is ready for acceptance testing.

3.4 Testing Process
The detailed testing process for each requirement is as follows:
1.
2.
3.
4.
5.
Installation of latest build.
Testing of the application in accordance to corresponding build release notes.
Submitting project problem reports for all errors and fail events found.
Following up with the developers.
Retesting when the developers fix the problems.
3.5 Program Unit Testing
Program Unit Testing is performed by the developers on the Programming Team who
implemented that particular program unit to verify that it performs according to its
intended design.
3.6 System Integration and Incremental Testing
After each feature of the software is unit tested, the feature is integrated into the system.
This testing will be performed to verify that the system satisfies the requirements
specified in the SRS. If there are any problems detected in the informal tests, test
engineer should record them in the PPRs and notify the design team about the problem
for proper disposition.
3.7 System Formal Qualification Testing
After all features of the software are integrated into the system, the formal software
qualification testing starts. These tests will be performed by the Software Test Team to
verify that the system satisfies the requirements specified in the SRS. Section 4.0 Test
Cases describes all test cases in the Formal Qualification Testing. Section 5.0 Test Log
lists all test results.
3.8 Project Problem Reports
Any errors should be recorded, reported and posted to the Binac Web site in the STP Test
log section when discovered in the test process. After errors have been corrected,
regression testing should be performed to verify that the error correction didn't break
some things else.
3.9 Environment Requirements
Testing is performed using hardware with the following minimum system requirements:
?
?
?
?
?
?
133 MHz Pentium
Microsoft Window, 98
32 MB RAM
10 MB available hard disk space
A display device capable of displaying 640x480 (VGA) or better resolution
Internet connection via a modem or network

3.10 Software Acceptance
When the software product satisfies the Binac team and passes all test cases, in
accordance with the STP, product achieves Software Acceptance.

4.0

T
EST
C
ASES

This section of the Software Test Plan documents test all test cases specified by Section
3.1 of the Software Requirements Specification. Therefore, all test cases in this section
shall be tested to demonstrate the functionality and quality of Comment Counter
application. Each test case shall be carried out following the each and every steps given
in the procedure section. All related results, information, and comments shall be
documented in Section 5 of the STP in a log format.