MSSE SOFTWARE, INC.

Test Plan for

MSSE-Golf Score
Version 1.0

Confidential and Proprietary Information of Datacard Worldwide

 Contents

1.0 INTRODUCTION 3

1.1. Objective 3

1.2. Project Description 3

1.3. Process Tailoring 3

1.4. Referenced Documents 3

2.0 ASSUMPTIONS/DEPENDENCIES 4

3.0 TEST REQUIREMENTS 4

4.0 TEST TOOLS 4

5.0 RESOURCE REQUIREMENTS 5

6.0 TEST SCHEDULE 5

7.0 RISKS/MITIGATION 5

8.0 METRICS 6

APPENDIX A – DETAILED RESOURCE REQUIREMENTS 8

APPENDIX B – DETAILED TEST SCHEDULE 9

APPENDIX C – TEST CASES 10

1.0 Introduction

1.1. Objective

This test plan describes the entire test activity for GolfScore Release 1.1 and
comprises of information on the scope of testing, how is the testing
accomplished through which test methodology. The test plan will identify the
requirements, assumptions/dependencies, test tools, resource requirements,
schedules, mitigation strategies, exclusions and risk.
This test plan serves as a living plan which will constantly adapt to reflect any
change requirements and the core team needs.

1.2. Project Description

The MSSE software on golf score aims to provide an insight on the performance
of golfers based on their score results for golf tournaments. A report will be
produced showing who has won the tournament and how the golfers performed
on the courses played.

1.3. Process Tailoring

The program will be developed in C or C++ that will be run on windows 2000 of
later versions of it. A command line interface will be present for users to execute
the program as such there will be no GUI for this program.
The follow test will be planned for the project:
Verification Testing - To ensure the requirements on the key functions of
GolfScore is being tested, this will be further grouped into specification testing
and functional testing. This would include Boundary Value Analysis &
Equivalence Partitioning techniques to select cases intelligently such that
scenarios are covered.
Entrance Testing – To ensure test data is sound by verifying different parameter
option and input data file formats.
Regression Test – To be put in place once from the development of the first
feature. Every time a new function is added the previous feature have to be
tested regressively.

1.4. Reference Document

Software Requirement Specification (SRS). Revision 1.1 18 July 2017

2.0 Assumptions/Dependencies
Assumptions (as per SRS 1.1)
• “Golfers are expected to play each course once” – For each course play is
>1
• “Number of golf courses specified for the tournament can be from 1 to 5” –
For each tournament the min number of course is >=1 and the max is <=
5
• “Golfers entered in the tournament can be from 2 to 12” - – For each
tournament the min number of golfers is >=2 and the max is <= 12

• Each golf course has 18 holes, and par for each hole is either 3, 4 or 5
stroke
• Thus, score and stroke count are not the same – “Stroke count have to be
converted to score”
• Golfer's score for a particular golf course is the sum of the scores for each
of the 18 holes. – “Score is based on Section 2.3.2 where by stroke count
gives a score”
• The lower a golfer’s stroke count (relative to par), the higher his or her
score for that hole – inverse correlation.
Dependencies
• Golfers must complete the golf course
• Score is based on the par and at least one stroke.

3.0 Test Requirements

Requirement Requirement Name Relevant SRS Section
number
1 Calling GolfScore 2.2
2 Tournament assumed requirements 2.3.1
3 Scoring metrics 2.3.2
4 Data input 2.4
• Individual Records
• Parameter on program call line
• Course Records
o Delimiter Record
• Golfer records
o Golfer’s Delimiter Record
5 Data Output (GolfScore) 2.5
• Tournament Ranking Record
 o List of Golfers, Score,
Standing
• Golfer Report
• Course Report
o List of golfers
o Hole by hole stroke
count
o Score
o Filename : course.rep
6 Error handling 2.6
• Input Parameter Errors
• Input Data Errors
• Errors on Output
7 Deliverables 3
• e.g GolfScore executable file
8 Performance Testing 4
• <1 minute

4.0 Test Tools

Test Management qTest

Test Design qTest
Defect Tracking Confluence
Functional Testing Junit, Manual
Performance Testing Jmeter
Test Coverage Monitor or Profiler Junit

5.0 Resource Requirements

Resource requirements for MSSE software:
Test Manager
Test automation engineer
System Tester
Test Designer

6.0 Test Schedule

Test Sequence Planned Actual Planned Actual Assumptions

Start Start Finish Finish
Date Date Date Date
 1.Test 1.Aug, 8.Aug, Requirements Given
Development 2017 2017
2.Module 9.Aug, 30.Aug, Development have
Availability 2017 2017 begun before 8 Aug
3. SVT Entrance 9.Aug, 16.Aug, Developers have
Testing 2017 2017 produced at least
one module
4. SVT Main 16.Aug, 30.Aug, Developers have
Testing 2017 2017 produced at least
one module
5. Build regression 30.Aug, 6.Aug, Developers have
test suite 2017 2017 produce main
feature
6.Performance 30.Aug, 6.Sep, Product ready
testing 2017 2017

7.0 Risks/Mitigation
Change in requirement Risk
Test plan is planned and scheduled to be ahead of project timeline of 6 weeks. 2
weeks buffer is available for any potential delays.
System downtime / Environmental Risk
Raise request for fix through respective personal responsible, escalate if
necessary. Test plan is planned and scheduled to be ahead of project timeline
of 6 weeks. 2 weeks buffer is available for any potential delays.

8.0 Metrics

1. Total number of test cases

2. Number of test cases passed
3. Number of test cases blocked
4. Number of defects found
5. Number of critical defects
6. Number of planned test hours
 7. Number of actual test hours
8. Number of bugs found product launched

Passed Test cases percentage can be derived above using 2. /3. x100
Fixed Defects percentage can be derive above using defects fixed/4 x100
Test design efficiency using above 1. / 7.
Appendix A – Detailed Resource Requirements

Role Minimum Specific Responsibilities

Resources
Recommended
Test Manager Jason Foo
Oversees the test plan and progress
• In charge of progress reporting to upper
management
• Provide technical consultation on test plan
and architecture
• Blockers and test resource management
Test Designer Jean Grey Identifies requirements, scopes, and implements
test cases
Responsibilities:
• Generate test plan
• Generate test suite architecture
• Evaluate test results
• Evaluate test efforts
• List the attributes and associations of test
data
System Tester Muhamad Ali Executes the tests
Responsibilities:
• Execute tests
• Log results
• Report defects
• Defects follow up
Test automation Dinesh Garauv Implement the test packages for unit test
engineer automation and functional test automation

• Creates the test classes and packages

implemented in the Test Suite.

• Create test assets if necessary

• Set up test environment for test automation

• Set up test data

Appendix B – Detailed Test Schedule
 Appendix C – Test Cases

Test Actual Expected

ID Scenario Pre-Condition Test Script Result Result
Calling GolfScore

Help information
Using command Key in Command should be
1 Help Info prompt >golf -h displayed

Input is in file in.txt Help information

Enter Command should be
Output is to be placed >golf -h c:\in.txt displayed on the
2 Help Info in C:\golfout golfout screen

Input is in file in.txt Course Report is

generated as per
Output is to be placed Enter Command the data in the
Course in C:\golfout >golf -c c:\in.txt in.txt file in folder
3 Report golfout golfout
Tournament
Ranking Report
Input is in file in.txt should be
generated as per
Output is to be placed Enter Command the data in the
Tournament in C:\golfout >golf -t c:\in.txt in.txt file in folder
4 Report golfout golfout
Golfer Report
should be
Input is in file in.txt generated as per
Enter Command the data in the
Output is to be placed >golf -g c:\in.txt in.txt file in folder
5 Golfer Report in C:\golfout golfout golfout
Course report &
Tournament
Ranking Report
Course should be
Report & Input is in file in.txt generated as per
Tournament Enter Command the data in the
Ranking Output is to be placed >golf -ct c:\in.txt in.txt file in folder
6 Report in C:\golfout golfout golfout
Course report +
Golfer Report
Input is in file in.txt should be
Course Enter Command generated as per
Report & Output is to be placed >golf -cg c:\in.txt the data in the
7 Golfer Report in C:\golfout golfout in.txt file in folder
 golfout

Generate the
Golfer Report +
Golfer Report Tournament
& Input is in file in.txt Ranking Report as
Tournament Enter Command per the data in the
Ranking Output is to be placed >golf -gt c:\in.txt in.txt file in folder
8 Report in C:\golfout golfout golfout
Course Report,
Golfer Report,
Tournament
Ranking Report
should be
Input is in file in.txt generated as per
Enter Command the data in the
Output is to be placed >golf -cgt c:\in.txt in.txt file in folder
9 All 3 reports in C:\golfout golfout golfout

Tournament Assumptions
1. In in.txt file,
enter no. of
tournament s
1
2. Enter
Command
Lower Range >golf -cgt
of number of Input file in.txt. c:\in.txt
1 Golf Courses golfout Report Generated
1. In in.txt file,
enter no. of
tournament s
5
2. Enter
Command
Upper Range >golf -cgt
of number of Input file in.txt. c:\in.txt
2 Golf Courses golfout Report Generated
 1. In in.txt file,
enter no. of
tournament s
6
2. Enter
Exceed Command
Range of >golf -cgt
number of Input file in.txt. c:\in.txt Report Not
3 Golf Courses golfout Generated
1. In in.txt file,
enter no. of
golfers 2
2. Enter
Command
Lower Range >golf -cgt
of number of Input file in.txt. c:\in.txt
4 Golfers golfout Report Generated
1. In in.txt file,
enter no. of
golfers 12
2. Enter
Command
Upper Range >golf -cgt
of number of Input file in.txt. c:\in.txt
5 Golfers golfout Report Generated
1. In in.txt file,
enter no. of
golfers 13
2. Enter
Exceed Command
Range >golf -cgt
number of Input file in.txt. c:\in.txt Report Not
6 Golfers golfout Generated

Scoring
1. In in.txt file,
mock up a
golfer, input
some scores.
2. Calculate the
scores
manually
3. Verify the
Score Input file in.txt. scores on the Scoring should
7 Calculation output file. match
Data Input

1. In file in.txt add

one course and label
C1

2.Save file
Input is in file in.txt Course report
3. Enter Command should be
Lower limit of Output is to be placed >golf -cgt c:\in.txt generated with
1 no.of course in C:\golfout golfout right data.
1. In file in.txt add
five course

2.Save file
Input is in file in.txt Course report
3. Enter Command should be
Upper limit of Output is to be placed >golf -c c:\in.txt generated with
2 no.of courses in C:\golfout golfout right data.
1. In file in.txt remove
all the course data

Input is in file in.txt 2.Save file

3. Enter Command Error should be
Output is to be placed >golf -cgt c:\in.txt displayed "Add a
3 No courses in C:\golfout golfout course name"
1. In file in.txt add six
course
Input is in file in.txt 2.Save file Error should be
3. Enter Command displayed "Too
Output is to be placed >golf -cgt c:\in.txt many course
4 Six courses in C:\golfout golfout names"

1. In file in.txt add

two golfers
Input is in file in.txt 2.Save file
3. Enter Command Report should be
Output is to be placed >golf -cgt c:\in.txt generated with
5 Two Golfers in C:\golfout golfout right data.

1. In file in.txt add

twelve golfers
Input is in file in.txt 2.Save file
3. Enter Command Report should be
Twelve Output is to be placed >golf -cgt c:\in.txt generated with
6 Golfers in C:\golfout golfout right data.
 1. In file in.txt remove
all golfers data
Input is in file in.txt 2.Save the file
3. Enter Command Error should be
Output is to be placed >golf -cgt c:\in.txt displayed " Golfers
7 Zero Golfers in C:\golfout golfout Data missing"
1. In file in.txt add
thirteen golfers and
data
Input is in file in.txt 2.Save the file
3. Enter Command Error should be
Thirteen Output is to be placed >golf -cgt c:\in.txt displayed "Too
8 Golfers in C:\golfout golfout many Golfers"
1. In file in.txt with
right data, add
course record with
par for holes as 3,4,5
values only
Course Input is in file in.txt 2.Save the file
Record - Par 3. Enter Command Report should be
for holes Output is to be placed >golf -cgt c:\in.txt generated with
9 3,4,5 in C:\golfout golfout right data.
1. In file in.txt with
right data, add
course record with
par for holes as 1,3,4
values only
Course Input is in file in.txt 2.Save the file
Record - Par 3. Enter Command Error should be
for holes with Output is to be placed >golf -cgt c:\in.txt displayed "Invalid
10 wrong value in C:\golfout golfout Par for Holes"
1. In file in.txt with
right data, add
course identifier as
Course "A"
Record - Input is in file in.txt 2.Save the file
Course 3. Enter Command Report should be
Identifier Output is to be placed >golf -cgt c:\in.txt generated with
11 Alphabet in C:\golfout golfout right data.
1. In file in.txt with
right data, add
course identifier as
Course "1"
Record - Input is in file in.txt 2.Save the file
Course 3. Enter Command Report should be
Identifier Output is to be placed >golf -cgt c:\in.txt generated with
12 number in C:\golfout golfout right data.
Data Output

Input is in file in.txt

Tournament Enter command The score for each
Ranking Output is to be placed >golf -t c:\in.txt course is exact as
1 Report - in C:\golfout golfout per the in.txt file

Input is in file in.txt Verify the Golfer's

Enter command rankings are true.
Golfer Final Output is to be placed >golf -t c:\in.txt Verify the list in
2 standing in C:\golfout golfout descending order

Input is in file in.txt Verify Golfers

Enter command records are as per
Golfer Report Output is to be placed >golf -g c:\in.txt the records in
3 - Golfer Score in C:\golfout golfout in.txt

Input is in file in.txt

Golfer Report Enter command Verify the records
- alphabetical Output is to be placed >golf -g c:\in.txt are sorted per last
4 listing in C:\golfout golfout names of Golfers

Course Input is in file in.txt

Report - Enter command Verify the course
number of Output is to be placed >golf -c c:\in.txt records are as per
5 Record in C:\golfout golfout the records in.txt

Input is in file in.txt

Course Enter command Verify the golfers
Report – Output is to be placed >golf -c c:\in.txt listing in each
6 Golfers in C:\golfout golfout course

Error Handling
1. In in.txt, enter the
characters * # invalid Appropriate
Input is in file in.txt characters. message should
Input 2. Enter command be displayed
parameter Output is to be placed >golf -c c:\in.txt report not
1 Errors in C:\golfout golfout generated.
Appropriate
In.txt file enter non message should
numeric data where be displayed
Input Data numeric data is report not
2 Errors input file is in.txt expected generated.
Performance

Process
Time to completes < 1
1 complete Execute the program minute.