10.

SOFTWARE TEST PLAN

10.1. Test Plan Identifier

The test plan identifier for the Sportaholics is the “Master Test Plan”, all test plans are covered under on
document. It is a high level plan for the project Sportaholics.

10.2. References
Following documents are referenced during the documentation:
[1] IEEE 829 Standard for Test Plan
[2] Sportaholics SQA plan

10.3. Introduction
This test plan describes the testing approach and overall framework that will drive the testing of the
Sportaholics. This document presents:

∙ Test Strategy: is a set of rules on which tests are being based on, including the givens of the project;
description of the process to set up a valid test like entry and exit criteria, creation of test cases, specific
tasks to perform, scheduling and data strategy for the Sportaholics.

∙ Execution Strategy: describes how the test is executed on the Sportaholics under development and
testing phase and process to identify and report bugs, issues and defects, and to fix and implement fixes,
and close the reported issues.

∙ Test Management: is a process to handle the logistics of the test and all the events that come up
during execution like communications, escalation procedures, and risk and mitigation.

10.3.1. Objectives
The objective of the test is to verify that the functionality of the project Sportaholics according to the
requirement specifications. The test will execute and verify the test scripts, identify, fix and retest all
high and medium severity defects, prioritize defects for future fixing. The final product of the test is
twofold:

∙ Production-ready software;

∙ A set of stable test scripts; that can be reused for overall performance and functional testing of the
Sportaholics.

10.3.2. Test Plan Overview

This test plan describes the overall testing approach and framework that will drive the testing for the
project Sportaholics. The next section of the document describes the test plan strategies used for the
testing of Sportaholics. The testing strategies will be applied at the Sportaholics during the development
Sportaholics

and testing phase of software development life cycle are Unit testing, Integration testing, Smoke testing,
Regression testing, System testing and User Acceptance testing. The next section describes the test
schedule when these testing strategies will be applied. Control activities, resources and software risk
items are referenced in the next sections respectively. The last few sections of this document describes
the features of the Sportaholics to be tested, feature pass/fail criteria, deliverables with milestones,
testing tasks, sign off template and filled template for the user acceptance test cases.

10.3.3. Relationship to Other Documents

The test plan document has direct relationship with the following document:

10.3.3.1. Connection with Requirement Analysis Document

The user acceptance test cases are designed and developed by referring to the use cases described in
the requirement analysis document. For each use case there will be at least one user acceptance test
case that validate and verify the use case functionality in detail.

10.3.3.2. Connection with System Design Document

The system level test cases will be designed and developed by referring to the system design document,
which describes the overall design of the Sportaholics. System design document describes all the
modules and their interfaces. The overall performance and functionality of the system will be tested by
implementing the integration test cases, smoke test cases and system test cases by following the system
design document of the Sportaholics.

10.4. Test Plan Strategy

The following test strategies shall be applied at the Sportaholics during the development and testing
phase:

10.4.1. Unit Testing

Unit testing shall be performed to verify and validate all modules of the system Sportaholics.

10.4.1.1. Definition
Unit testing is a level of software testing where individual units/ components of software are tested. The
purpose is to validate that each unit of the software performs as designed. A unit is the smallest testable
part of any software. It usually has one or a few inputs and usually a single output.

10.4.1.2. Participants
Developers shall be testing the each component by developing and testing the unit test cases before
submitting the changes at main development stream. After submission QA will test the components
using the already developed unit test cases.

MS Research Project Page 2 of 24

Sportaholics

10.4.1.3. Methodology

Manual testing shall be performed by designated team of developers of each unit being developed and
before its delivery to the testing team. After submission testing team shall be performing the testing in
an automated way.

10.4.2. Integration Testing

10.4.2.1. Definition
Integration testing is a software development process which program units are combined and tested as
groups in multiple ways.

10.4.2.2. Participants
This testing will be performed by the software quality assurance team in order to validate that the
features have been integrated properly and the desired functionality is being achieved.

10.4.2.3. Methodology

Developers shall initially perform integration testing and after submission QA shall perform automated
testing.

10.4.3. Smoke Testing

10.4.3.1. Definition
Smoke testing is done in order to verify the build that has been deployed for testing is working fine and
the most important features such as deployment of build is done successfully or not.

10.4.3.2. Participants
QA team shall be performing the smoke testing.

10.4.3.3. Methodology

QA team shall be performing the smoke testing in an automated way.

10.4.4. Regression Testing

10.4.4.1. Definition
Regression testing is done in order to verify that the newly added functionality do not causes any change
or issue in the already developed units and the application works fine in for tested cases.

10.4.4.2. Participants
QA team shall be performing the regression testing.

10.4.4.3. Methodology

Regression testing shall be performed by QA team in an automated way.

MS Research Project Page 3 of 24

Sportaholics

10.4.5. System Testing

10.4.5.1. Definition
System testing is performed at a complete and integrated system, in order to ensure the system’s
compliance with the specified system requirements.

10.4.5.2. Participants
QA team shall be responsible for the system testing and monitoring the system performance and
functionality.

10.4.5.3. Methodology
System testing shall be performed by QA in an automated way.

10.4.6. User Acceptance Testing

10.4.6.1. Definition
User acceptance testing is the last phase of software development life cycle when the end user actually
tests the software to make sure it can handle required tasks in real world scenarios according to the
specifications.

10.4.6.2. Participants
End users of the Sportaholics shall be conducting the user acceptance scenarios.

10.4.6.3. Methodology
End users of the Sportaholics shall be performing the user acceptance tests in a manual way.

10.5. Test Schedule

Test Activities Begin End Responsibility

QA Plan 15/02/2019 06/05/2019 QA Team

Test Cases Execution 25/08/2019 28/11/2019 QA Team

Unit Testing 14/08/2019 22/11/2019 Development Team

Integration Testing 14/08/2019 22/11/2019 QA Team

Smoke Testing 14/08/2019 01/11/2019 QA Team

Regression Testing 20/11/2019 28/11/2019 QA Team

System Testing 14/08/2019 20/11/2019 QA Team

User Acceptance Testing 21/10/2019 22/11/2019 QA Team

MS Research Project Page 4 of 24

Sportaholics

10.6. Control Activities

A follow up meeting shall be held each week and after the delivery of each milestone to discuss the
testing status of the system. Following points shall be discussed in meeting during discussion session:

● Testing Status Report

● Software Progress and Reported Issues

10.7. Resources
The human resources involved in these activities are:

● Project manager
● Development leads
● QA leads
The non-human resources involved are:

● Jira
● Visual studio
● Pycharm community edition

10.8. Software Risk Items

Following are the risks that may occur during the testing of the Sportaholics:

● Unavailability of human resources

● Unavailability of hardware and software resources
● Change in requirements
● Late delivery/ missed a milestone

10.9. Features to be tested

All features of the Sportaholics shall be tested.

10.10. Item Pass/Fail Criteria

If an item satisfies the criteria written in the test case specifications then it shall be considered pass.

If an item shall not fulfill the criteria written in the test specifications; and the expected and actual result
of the test case is not same then the test case shall be considered as fail.

If an item expected and actual result of the test case is same, the test case shall be considered as pass.

10.11. Deliverables
Following are the deliverables of the software test plan:

MS Research Project Page 5 of 24

Sportaholics

● QA Plan
● Test Cases
● Issues Summary Report
● Test execution Summary Report

10.12. Testing Tasks

Following tasks are included in testing phase

● Test plan preparation

● Test cases preparation
● Hardware testing environment preparation
● Software testing environment preparation
● Database preparation for testing environment
● Test cases execution
● Faults reporting
● Prepare testing summary report

10.13. Sign Off

Dr. Ghulam Ahmad Farrukh is responsible for the approval of the test plan of Sportaholics.

10.14. Test Cases

10.14.1. Registration
Test Case ID: TC-01

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 21/10/2019

Test case Execution Status: PASS

Use Case Reference(s): UC1

GUI Reference(s): UI1

Objective: User has successfully registered at website.

Product Module: Login

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open.

MS Research Project Page 6 of 24

Sportaholics

Description: User Registration

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the 1. System 1. System PASS N/A

“Register” button. displays a form displays a form
to the user. to the user.
2. User Fills in the required
information in the form and 2. System 2. System
clicks on the “Submit” displays a displays a
button. message to user message to user
which says “You which says “You
have successfully have successfully
registered with registered with
Sportaholics”. Sportaholics”.

Comments: N/A

Test Case ID: TC-02

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 21/10/2019

Test case Execution Status: PASS

Use Case Reference(s): UC2

GUI Reference(s): UI2

Objective: User has to successfully log in.

Product Module: Login

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user is already registered.

MS Research Project Page 7 of 24

Sportaholics

Description: User Log in

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the “Login” 1. System 1. System PASS N/A

button. displays a form displays a form
to the user. to the user.
2. User Fills in the required
information in the form and 2. The system 2. The system
clicks on the “Submit” will redirect the redirected the
button. user to the user to the
homepage homepage
labeled “The labeled “The
Turf”. Turf”.

Comments: N/A

Test Case ID: TC-03

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 21/10/2019

Test case Execution Status: PASS

Use Case Reference(s): UC3

GUI Reference(s): UI3

Objective: User has to successfully log out.

Product Module: Login

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user is already registered and logged in.

Description: User Log Out

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

MS Research Project Page 8 of 24

Sportaholics

1. User clicks on the “Log 1. Redirection of 1. Redirection of PASS N/A

Out” button. user to the main user to the main
homepage of the homepage of the
website. website after
successfully log
out.

Comments: N/A

Test Case ID: TC-04

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 23/10/2019

Test case Execution Status: PASS

Use Case Reference(s): UC4

GUI Reference(s): UI4

Objective: User has to successfully create an event.

Product Module: Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: User must be on “The Turf” page of the website.

Description: Event Creation

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the 1. System will 1. System PASS N/A

“Create Event” button display a list of displays a list of
given on the “The Turf” available sports available sports
page. type to the user. type to the user.

2. User selects their 2. System will 2. System

preferred sport. display a list of displays a list of
available venues available venues
3. User selects their to the user.

MS Research Project Page 9 of 24

Sportaholics

preferred venue. 3. System will to the user.

prompt the user
4. User enters the to enter the 3. System
minimum number of prompts the user
minimum
required players. number of to enter the
minimum
5. User enters a starting players.
number of
time for the event. 4. System will players.
prompt the user
to choose a 4. System
prompts the user
starting time.
to choose a
5. System will starting time.
display a success
message and will 5. System
displays a success
add event details
to “Upcoming message and
adds event
Events”.
details to
“Upcoming
Events”.

Comments: N/A

Test Case ID: TC-05

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 23/10/2019

Test case Execution Status: PASS

Use Case Reference(s): UC5

GUI Reference(s): UI5

Objective: User has to successfully view available events.

Product Module: Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

MS Research Project Page 10 of 24

Sportaholics

Pre-requisite: User must be on “The Turf” page of the website.

Description: View available Events

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the “View 1. System will 1. System PASS N/A

Available Events” button display a map to displays a map to
given on the “The Turf” the user with the user with
page. markers. markers.

Comments: N/A

Test Case ID: TC-06

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 29/10/2019

Test case Execution Status: PASS

Use Case Reference(s): UC6

GUI Reference(s): UI6

Objective: User has to successfully join an event.

Product Module: Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: User must be on “The Turf” page of the website.

Description: Join Events

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the “View 1. System will 1. System PASS N/A

Available Events” button display a map to displays a map to
given on the “The Turf” the user with the user with
page. markers. markers.

MS Research Project Page 11 of 24

Sportaholics

2. User clicks on the desired 2. System will 2. System

sporting event’s marker display the displays the
which they wish to join. details of the details of the
selected sporting selected sporting
3. User clicks on the “Join event. event.
Event” option given at the
bottom right hand corner 3. System will 3. System enrolls
of the details of the enroll the user in the user in the
selected event. the selected selected event
event and will and displays a
display a success success message.
message.

Comments: N/A

Test Case ID: TC-07

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 29/10/2019

Test case Execution Status: PASS

Use Case Reference(s): UC7

GUI Reference(s): UI7

Objective: User has to successfully exit from the joined event.

Product Module: Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has joined event/s.

Description: Exit Event

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the “Exit 1. System will 1. System PASS N/A

Event” option from the remove the user removes the user
details of the event. from the from the

MS Research Project Page 12 of 24

Sportaholics

corresponding corresponding
event. event.

Comments: N/A

Test Case ID: TC-08

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 29/10/2019

Test case Execution Status: PASS

Use Case Reference(s): UC8

GUI Reference(s): UI8

Objective: User has to successfully cancel an event.

Product Module: Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has joined event/s.

Description: Cancel Event

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the event 1. System will 1. System PASS N/A

which they want to exit. remove the removes the
event from the event from the
user’s “My user’s “My
Upcoming Upcoming
Events” section. Events” section.

2. System will 2. System

generate a generates
cancelation alert cancelation alert
to all enrolled to all enrolled
players. players.

MS Research Project Page 13 of 24

Sportaholics

Comments: N/A

Test Case ID: TC-09

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 05/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC9

GUI Reference(s): UI9

Objective: User has to successfully change his/her preference.

Product Module: Profile

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has created a profile.

Description: Change User Preference

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the “My 1. System will 1. System takes PASS N/A
Profile” section on their take the user to a the user to a new
“Turf”. new page which page which
shows the user’s shows the user’s
2. User changes the current current
preferences which they preferences in an preferences in an
want to modify, add or editable form. editable form.
delete and clicks on “Save
preferences”. 2. System will 2. System saves
save the user’s the user’s
updated updated
preferences. preferences.

Comments: N/A

MS Research Project Page 14 of 24

Sportaholics

Test Case ID: TC-10

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 05/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC10

GUI Reference(s): UI10

Objective: User has to successfully edit event details.

Product Module: Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has created event/s.

Description: Edit Event Details

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the event 1. System will 1. System takes PASS N/A
which they want to edit. take the user to a the user to a new
new editable editable page of
2. User changes the desired page of details of details of
details of the event and corresponding corresponding
clicks on the “Save event. event.
Changes” button.
2. System will 2. System takes
take the user the user back to
back to their their “Turf”.
“Turf”.

Comments: N/A

Test Case ID: TC-11

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

MS Research Project Page 15 of 24

Sportaholics

Test Case Version: 1.1

Test Execution Date: 05/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC11

GUI Reference(s): UI11

Objective: User has to search for event/s.

Product Module: Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has logged in.

Description: Search Event

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User enters the name of 1. System will 1. System takes PASS N/A
the event which they want take the user to a the user to a new
to search in the Search bar new page of page of
given at the top of the corresponding corresponding
“Turf” page. event’s details. event’s details.

Comments: N/A

Test Case ID: TC-12

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 05/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC12

GUI Reference(s): UI12

Objective: User has to invite players for an event.

MS Research Project Page 16 of 24

Sportaholics

Product Module: Event and Notification

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has logged in.

Description: Invite Player to an Event

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User enters chooses the 1. System will 1. System PASS N/A

event to which they want display the event displays the
to invite a specific player. details to the event details to
user. the user.
2. User clicks on the “Invite
player” option from the 2. System will 2. System
event details. prompt user to prompts user to
enter the email enter the email
3. User enters the email ID ID of the player. ID of the player.
of the player they wish to
invite. 3. System will 3. System
generate an generates an
HTML link for the HTML link for the
event and will event and sends
send email. email.

Comments: N/A

Test Case ID: TC-13

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 05/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC13

GUI Reference(s): UI13

Objective: User has to update data in his/her profile.

MS Research Project Page 17 of 24

Sportaholics

Product Module: Profile

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has logged in.

Description: Add Player Data

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the “My 1. System will 1. System PASS N/A

Profile” section of the main display the displays the
page labeled “Turf”. profile details to profile details to
the user in an the user in an
2. User enters the details editable form. editable form.
they wish to add to their
profile and clicks on the 2. System will 2. System saves
“Save” button. save the user’s the user’s profile.
profile.

Comments: N/A

Test Case ID: TC-14

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 21/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC14

GUI Reference(s): UI14

Objective: User has to schedule an already created event.

Product Module: Schedule and Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

MS Research Project Page 18 of 24

Sportaholics

Pre-requisite: Sportaholics website is open and user has logged in.

Description: Schedule an Event

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the 1. System will 1. System PASS N/A

“Schedule Event” button on prompt the user prompts the user
the “Turf” page. to enter the date to enter the date
time and venue time and venue
2. User provides their for the event. for the event.
desired date, time and
venue for the event. 2. System will 2. System
schedule the schedules the
event and will event and adds
add the details of the details of the
the event in the event in the
Upcoming Upcoming
Event’s list. Event’s list.

Comments: N/A

Test Case ID: TC-15

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 21/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC15

GUI Reference(s): UI15

Objective: User has to add venue details in an already created event.

Product Module: Venue

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has logged in.

MS Research Project Page 19 of 24

Sportaholics

Description: Add a Venue

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. Admin user clicks on the 1. System will 1. System PASS N/A

“Manage Venues” section redirect to a new redirects to a
on the homepage. page that shows new page that
details of the shows details of
2. User clicks on the “Add currently the currently
Venue” button. registered registered
3. User pinpoints the exact venues. venues.
location of the sporting 2. System will 2. System
venue, specifies a name for display a map to displays a map to
the venue and clicks on the user, and the user, and
“Save Venue” button. prompts to prompts to
pinpoint the pinpoint the
location. location.

3. System will 3. System saves

save the location the location and
and name of the name of the
venue. venue.

Comments: N/A

Test Case ID: TC-16

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 21/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC16

GUI Reference(s): UI16

Objective: User has to edit venue details in an already created event.

Product Module: Venue and Event

MS Research Project Page 20 of 24

Sportaholics

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has logged in.

Description: Edit a Venue

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. User clicks on the 1. System will 1. System PASS N/A

“Manage Venues” section. redirect to a new redirects to a
page showing new page
2. User clicks on the name currently showing
of the venue which they registered currently
want to edit. venues. registered
3. User makes the desired venues.
2. System will
changes in the venue’s display a map to 2. System
details and clicks on “Save the user, and displays a map to
Venue” button. prompts to the user, and
pinpoint the prompts to
location. pinpoint the
location.
3. System will
save the updated 3. System saves
information of the updated
venue. information of
venue.

Comments: N/A

Test Case ID: TC-17

QA Test Engineer: Saad Munir Reviewed By: Saad Munir

Test Case Version: 1.1

Test Execution Date: 21/11/2019

Test case Execution Status: PASS

Use Case Reference(s): UC17

GUI Reference(s): UI17

MS Research Project Page 21 of 24

Sportaholics

Objective: User has to delete venue details in an already created event.

Product Module: Venue and Event

Environment: Website under test in Google Chrome

Assumptions: Website is deployed.

Pre-requisite: Sportaholics website is open and user has logged in.

Description: Delete a Venue

Input Parameters Expected Output Actual Output Status Possible Reason(s) in

case of failure

1. Admin user clicks on the 1. System will 1. System PASS N/A

“Manage Venues” section redirect to a new redirects to a
on the homepage. page showing new page
currently showing
2. User clicks on the name registered currently
of the venue. venues. registered
3. User clicks on the venues.
2. System will
“Delete” button. confirm the 2. System
deletion from confirms the
user. deletion from
user.
3. System will
remove the 3. System
venue from the removes the
“Manage venue from the
Venues” page “Manage
Venues” page.

Comments: N/A

10.14.2

10.15. Conclusion
This software test plan describes all the software features of the Sportaholics to be tested, types of
testing to be applied at these features, passing and failing criteria of the features under testing. The
complete description of test cases describes the schedule along the owner details, test purpose,

MS Research Project Page 22 of 24

Sportaholics

execution date, reported bugs and etc. Moreover, this plan is a tentative plan and may be modified in
later stages of SDLC.

MS Research Project Page 23 of 24

Sportaholics

11. LESSONS LEARNT

Over the course of designing and documenting this project, we have learnt a few valuable lessons.

Given below is a list of those lessons:

1. Do not leave any deliverable until till the last day. Time is always of the essence.

2. Do not underestimate the importance of communication. Regular meetings between team

members are extremely important and they should always be done in person.

3. Each and every team member should treat the whole product as their own and should not
follow the “not my job” principle.

4. The manager must know the capabilities of his/her team members and should always know
which member is rightly suited for the job.

5. When things get chaotic, finger pointing is bound to happen between team members and this is
where the manager’s abilities are tested the most. The manager must step in at the time of
chaos and panic and should keep his/her cool to make things right and settle the nerves.

6. Foresightedness is very important in order to make a project successful.

7. Always try to see the bigger picture, try to analyze the impacts of the actions that are being
taken.

8. As a project manager, we must always be proactive.

9. We must always try to foresee problems before they arise.

10. Everything that can go wrong; will go wrong at the worst possible time. Therefore, hope for the
best but be prepared for the worst.

MS Research Project Page 24 of 24