MSSE SOFTWARE, INC

Test Plan for GolfScore

Revision 1.1

Written by: NASAR KHAN

Confidential and Proprietary Information of Datacard Worldwide

 Contents

1.1 INTRODUCTION 3
1.1. Objective 3

1.2. Project Description 3

1.3. Process Tailoring 3

1.4. Referenced Documents 3

2.1 ASSUMPTIONS/DEPENDENCIES 3

3.1 TEST REQUIREMENTS 4

4.1 TEST TOOLS 4

5.1 RESOURCE REQUIREMENTS 4

6.1 TEST SCHEDULE 5

7.1 RISKS/MITIGATION 5

8.1 METRICS 5

APPENDIX A - DETAILED RESOURCE REQUIREMENTS 6

APPENDIX B - DETAILED TEST SCHEDULE 7
1.1 Introduction

1.1. Objective
The test strategy for GolfScore Release 1.1 is detailed in this document. It contains information on what should be tested, how testing should
be done, and what should not be tested. A description of the testing schedule, tests to be executed, test dependencies, resources necessary,
testing tools, and metrics are also included in this document. Changes in the team's structure and needs must constantly be reflected in this
document.
The primary goal of this test is to check the GollfScore program's software requirements specification (SRS), which may be found in
Appendix A.
1.2. Project Description
GolfScore is a software that generates results for golf tournaments for players on each course. This software accepts a text file as input (as
specified in the SRS) and creates three text files as output (also described in the SRS).

1.3. Process Tailoring

There are no external dependencies required for the GolfScore application. As a result, in the context of Design Verification and System
Validation, the test plan is adjusted along Functional and Non-functional Testing. The following steps govern the testing process:
Entrance Test:
To ensure that the software can be performed successfully and that input parameter errors are handled according to the SRS.
The Entrance Testing test scenarios are described in Appendix C, while the SRS is described in Appendix A.
Main Test:
To ensure that the software is executed correctly. To see if the software processes the input data correctly and provides the expected
results. The program's handling of input data errors and output errors is also double-checked for accuracy.
The Main Testing test scenarios are described in Appendix C.
Exit Test:
To ensure that the software generated the needed outputs and stored them in the appropriate format and place.
Exit Testing test cases may be found in Appendix C.
Regression Test:
All tests are performed again to guarantee correct behaviour after faults have been detected and handled during testing.

2.1 Assumptions/Dependencies
The development team is expected to unit test their code as well as do integration testing while building the program. Field employees, in
collaboration with customers, are expected to conduct customer validation testing.
The program must be accessible by September 4, 2021, in order to meet the deadline.

3.0 Test Requirements

Entrance Tests:
• The application is built in C or C++ and operates on a PC running Windows 2000 or later versions of Windows.
• The program will execute as an independent executable.
 • The command line prompt can be used to run the application.
• With valid input parameters, the application is run.

Main Tests:

 The event must have a minimum of one and a maximum of five golf courses.

 Every golfer is required to play each course at least once.

 The number of golfers in the competition might range from two to twelve.

 Each course's par must be 3, 4, or 5 on each hole.

 A golfer's score for each hole played ranges from 0 to 6. (0 and 6 included).

 The initial set of entries in the input file (course records) exists and each item follows the desired format.

 The end of course records is signaled by a delimiter record.

 The end of the input file is signaled by a delimiter record.

Exit Tests:
 The software should generate a number of reports based on the choices selected.
 The produced reports should be stored as text files with the extension ".rep" in the given output directory (or, if not provided, in the
directory of the input file).
 If asked, a list of all golfers in the chosen format should be included in the event ranking report. The list should be stored with the
filename trank.rep and should be in decreasing order of final score.
 If asked, a list of all golfers in the given format should be included in the golfer report.
 If desired, a section for each Golf Course specified in the input Course Records in the course report should be included.

4.1 Test Tools

To aid the testing process, the following testing tools are required:
• Defect reporting and tracking software
• Installation media for multiple Windows versions above 2000 (e.g. XP, Vista, 7, 8, 8.1, & 10)

5.1 Resource Requirements

The following resource would be required:
• GolfScore Program verson 1.1
• Three PCs capable of hosting virtual machines
• A virtualization software
• Three Test Group personnel with at least 70% of his/her time available for this effort. See Appendix A for details.
6.1 Test Schedule
No. Test Start Finish

1 Test Development 22.12.2020 04.01.2021

2 Program Availability 04.01.2021 --
3 Entrance Testing 05.01.2021 11.01.2021
4 Main Testing 12.01.2021 24.01.2021
5 Exit Testing 24.01.2021 30.01.2021

6 Regression Testing 31.01.2021 05.02.2021

See Appendix B for details.

7.1 Risks/Mitigation
There is a considerable risk of input data mistakes without a software that enforces compliance in the structure of input data.

8.1 Metrics
The following metrics data will be collected. Some will be collected prior to, and some after product shipment.

Prior to shipment:
Effort expended during DVT, SVT and Regression
# of defects uncovered during DVT, SVT and Regression, and development phase each defect is attributable to
Test tracking S-Curve
PTR S-Curve

After shipment:
# of defects uncovered and development phase each defect is attributable to Size of software

Appendix A - Resource Requirements

No. Test No of Personnel No of Hours

1 Test Development 2 70
2 Entrance Testing 2 30
3 Main Testing 2 70
4 Exit Testing 2 30
5 Regression Testing 2 20
 Virtual machine-capable computers are necessary so that the application may be tested on different versions of Windows.
 Virtualization software is necessary in order to test the application on several versions of Windows.
Appendix B - Detailed Test Schedule
No. Test Start Finish

1 Test Development 22.12.2020 04.01.2021

2 Program Availability 04.01.2021 --

3 Entrance Testing 05.01.2021 11.01.2021
4 Main Testing 12.01.2021 24.01.2021
5 Exit Testing 24.01.2021 30.01.2021

6 Regression Testing 31.01.2021 05.02.2021

No. Test Dependencies

Test Development 3 PCs
1
3 Personnel
2 Program Availability GolfScore Program
3 Entrance Testing 3 PCs
3 Personnel
Virtualization Software
4 Main Testing 3 PCs
3 Personnel
Virtualization Software
5 Exit Testing 3 PCs
3 Personnel
Virtualization Software
6 Regression Testing 2 PCs
2 Personnel Virtualization Software
Appendix C - Test Cases
Test No. Test Case Test Type
1 The program shall be written in C or C++ Non-functional
2 The program shall run on a PC running Windows 2000 Non-functional
3 The program shall run on a PC running Windows XP Non-functional
4 The program shall run on a PC running Windows Vista Non-functional
5 The program shall run on a PC running Windows 7 Non-functional
6 The program shall run on a PC running Windows 8 Non-functional
7 The program shall run on a PC running Windows 10 Non-functional
8 The program shall run as a stand-alone executable Non-functional
9 The program shall run from the command line prompt Non-functional
10 Command line options “-c -t -g” shall be accepted Functional
11 Command linerecord
optionshall
“-k”beshall display an “unrecognizable options” Functional
this. The first used and processing shall continue.
28 message
The number of golfers “0” shall return an error Functional
29 Command
The numberline of option
golfers“-j”
“1” shall
shall display
return an anerror
“unrecognizable options” Functional
Functional
12
30 message
The number of golfers “2” shall be accepted Functional
31 Command
The numberline of option
golfers“-kj”
“12” shall
shall display
be acceptedan “unrecognizable options” Functional
Functional
13
32 message
The number of golfers “13” shall return an error Functional
14 Command Functional
33 Par for holeline “2”option “-ckj”an
shall return shall display an “unrecognizable options”
error Functional
34 message
Par for hole “6” shall return an error Functional
Specifying Functional
35
15 Par for holean “3”input
shallfilename that does not exist shall display an “input
be accepted Functional
parameter error”
36
16 Par for holean
Specifying “4” shall directory
output be accepted that does not exist shall display an “input Functional
Functional
37 Par for hole
parameter error” “5” shall be accepted Functional
38 Golfer
Command score peroption
line hole “7”
“-g”shall
shallreturn an errorand shall display help
be accepted Functional
17
39 Golfer score per hole “-1” shall return an error Functional
information
40 Golfer
Callingscore per holeas“0”
the program shall
“golf be in.txt
-ctg accepted
golfout” where “in.txt” exists Functional
Functional
18
41 Inputisdata Functional
and validwithandnon-numeric
folder “golfout” dataexists
whereshallnumeric data is expected shall
be accepted
return an error
Calling the program as “golf -ctg in.txt golfout dis” where “in.txt” exists Functional
19
42 Inputisdata Functional
and validwithandnumeric data where
folder “golfout” non-numeric
exists data is expected shall
shall be accepted
20 return an error
Calling the program as “golf -ctg in.txt golfout” where “in.txt” exists Functional
43 Input
and isdata
validthatandviolates delimiter does
folder “golfout” constraints
not exist shall return
shall an error
display an “input Functional
44 Input file that
parameter error” does not contain course records shall return an error Functional
45
21 Input
Callingfilethethat does not
program as contain
“golf -ctggolfer
in.txtrecords
golfout” shall return
where an error
“in.txt” does not Functional
46 The command line arguments "-ctg"
exist shall display an “input parameter error” will create three output files: Functional
22 "trank.rep,"
The number "golfer.rep,"
of golf course and“1”"course.rep."
shall be accepted If any of the files already Functional
23 exist, the userofwill
The number golfbecourse
asked“5” with a notice
shall stating that the file exists and
be accepted Functional
24 asking if theyofwant
The number golf to overwrite
course it. return an error
“-5” shall Functional
25 The number of golf course “6” shall return an error Functional
47
26 Calling
The numberthe program with command
of golf course “0” shall line
returnoption “-c” shall generate an
an error Functional
Functional
37 output file: “course.rep”. If the file already
Having multiple records for a golfer on the same golf exists, the user shall
courses be be
shall Functional
prompted with a message
accepted, although a messagethat should
says thebefile already to
displayed exists and asking
indicating
whether to overwrite it or not.
48 Functional
When you run the programme with the -t option, you'll get a file named
"trank.rep" as an output. If the file already exists, the user will be asked
with a notice stating that it does and asking if they want to replace it.
49 The output file when running the programme with the command line Functional
option "-g" is "golfer.rep." If the file already exists, the user will be
asked with a notice stating that it does and asking if they want to replace
it.
50 The software will display an error if the output cannot be stored owing Functional
to inadequate permissions.