Online Audio Player - STQA_Mini_Project2.pdf

Test Plan
Project name: Online Audio Player
Prepared by:
Date:25.11.2021
Rohan Mandhare
Nikhil Thapa
Prajwal Jadhav
Bandu Sakhare

TABLE OF CONTENTS
1. Introduction
2. Objectives and Tasks
2.1. Objectives
2.2. Tasks
3. Scope
4. Testing Strategy
4.1. Alpha Testing (Unit Testing)
4.2. System and Integration Testing
4.3. Performance and Stress Testing
4.4. User Acceptance Testing
4.5. Automated Regression Testing
4.6. Beta Testing
4.7. Compatibility Testing
5. Hardware Requirements
6. Environment Requirements
7. Test Schedule
8. Control Procedures
9. Features to be Tested
10. Features not to be Tested
11. Resources/Roles & Responsibilities
12. Schedules
13. Risks/Assumptions
14. Tools
15. Approvals

1.0 INTRODUCTION
Online Audio Player is basically a website that facilities the user with two media
options. Online Media Player consist of both audio player and video player
options. The media player has user friendly interface so the user can easily
navigate between the tabs and experience the better quality of music and video.
Audio Player had lots of music options like classical, pop, rap, remix, and much
more. All songs in the audio player has relative themes that will enhance the
overall music experience. The another major part of online media player is video
player. Video Player consist of various types of the video songs with high quality
video experience. There is scope to upload the video songs in the video player so
that you can use them in future. Anyone can easily get familiar with the user
friendly interface of the media player.
There are four major modules in this project:
• Register/Login module
• Home Page module
• MP3/Audio Player module

2.0 OBJECTIVES AND TASKS
2.1 Objectives of Test Plan
• Verify that the functionality of Online Media Player meets the full
requirements, including quality requirements (functional and non-functional
requirements) and fit metrics for each quality requirement and satisfies the use
case scenarios and maintain the quality of the product.
• Any changes, additions, or deletions to the requirements document, Functional
Specification, or Design Specification will be documented and tested at the
highest level of quality allowed within the remaining time of the project and
within the ability of the test team.
• Identify and expose all issues and associated risks, communicate all known
issues to the project team, and ensure that all issues are addressed in an
appropriate matter before release.
2.2 Tasks of Test Plan
Sr.
No.
Business
Requirements
(BR)
Functional
Requirements
(FR)
Test Scenarios
(TS)
Testing Approaches
/Strategies (TA)
01 Allow users to
search URLs and
browse through
web pages
Web Layout
i. Search URLs
ii. Create
Bookmarks
and History
1. Functional Testing
(Standard Testing)
2. Non-Functional
Testing

3.0 SCOPE
Module Name Applicable Roles Description
Register/Login Users New users can create account and
existing users can log into the
system using their credentials.
Home Page Users All users can navigate between
various tabs through home page.
Users had options to select either
from audio or video player.
MP3/Audio Player Users Users get high quality music along
with themes related each song.
Video Player Users Users get the high resolution video
songs they can easily navigate
between their favourite songs. Users
can easily upload their songs.
4.0 TESTING STRATEGY
- Understanding Requirements:
• Requirement specifications will be sent by client.
• Understanding of requirements will be done by QA
- Preparing Test Cases:
QA will be preparing test cases based on the exploratory testing. This will cover
all scenarios for requirements.
- Preparing Test Matrix:
QA will be preparing test matrix which maps test cases to respective
requirement. This will ensure the coverage for requirements.
- Reviewing test cases and matrix:
• Peer review will be conducted for test cases and test matrix by QA Lead

• Any comments or suggestions on test cases and test coverage will be provided
by reviewer respective Author of Test Case and Test Matrix
• Suggestions or improvements will be re-worked by author and will be send for
approval
• Re-worked improvements will be reviewed and approved by reviewer Test Plan
- Creating Test Data:
Test data will be created by respective QA on client's developments/test site based
on scenarios and Test cases.
- Executing Test Cases:
• Test cases will be executed by respective QA on client's development/test site
based on designed scenarios, test cases and Test data.
• Test result (Actual Result, Pass/Fail) will updated in test case document Defect
Logging and Reporting: QA will be logging the defect/bugs in Word document,
found during execution of test cases. After this, QA will inform respective
developer about the defect/bugs. - Retesting and Regression Testing: Retesting
for fixed bugs will be done by respective QA once it is resolved by respective
developer and bug/defect status will be updated accordingly. In certain cases,
regression testing will be done if required.
- Deployment/Delivery:
• Once all bugs/defect reported after complete testing is fixed and no other bugs
are found, report will be deployed to client’s test site by PM.

• Once round of testing will be done by QA on client’s test site if required Report
will be delivered along with sample output by email to respective lead and Report
group.
• QA will be submitting the filled hard copy of delivery slip to respective
developer.
• Once lead gets the hard copy of delivery slip filled by QA and developer, he
will send the report delivery email to client.
Approach
Type of
Testing
Manual
Testing
Autom
ated
Testing
on
Device
Tools/APIs/Libraries
Using
Device
Using
Emulator
Standard
Testing
(Functiona
l Testing)
Unit Testing Yes Yes No
Selenium
Integration
Testing
Yes Yes No
System
Testing
Yes No Yes
Regression
Testing
Yes No Yes
Acceptance
Testing
Yes No No
Special
Type of
Testing to
Address
Specific
Challenge
Compatibilit
y Testing
Yes No Yes
GUI Testing Yes No No
Client
specific
Testing
Performance
Testing
- - -
Security
Testing

4.1 Unit Testing
Definition:
A unit test is a way of testing a unit - the smallest piece of code that can be
logically isolated in a system.
Participants: Rohan Mandhare , Bandu Sakhare
Methodology:
MODULE/FUNCTIONALITY
NAME:
Register/Login
UNIT/CLASS: sign-in, Register, logout
CREATED BY: Bandu Sakhare
DATE OF CREATION: 5.11.2021
DATE OF REVIEW 25.11.2021
TEST
CAS
E
ID
TEST
UNIT/CLA
SS
TES
T
CAS
E
PRE-
CONDITI
ON
TEST STEPS TEST DATA
EXPECT
ED
RESUL
T
POST
CONDITI
ON
ACTU
AL
RESU
LT
STATUS
(PASS/FAIL)
#1 sign-up 1 Display
s
Home
Web
Layout
1. Launch
theapp
2. Click
on
“Crea
te
Acco
unt"
3. Enter
require
d user
details
Name:
Rohan Mandhare
Email:
rohanmandhare1999
@g mail.com
Mobile: 7387727176
Password: *****
Enters
the
user’s
profile
(
Prasad
Shinde
)
Should
enter the
user page
or show
errors in
the fields
of
improper
validation
s
Enters
the
user’s
profile
PASS
#2 sign-in 4 Display
s Home
Web
Layout
1. Launch
theapp
2. Enter
user
accoun
t
details
Email:
rohanmandhare1999
@g mail.com
Password: *****
Enters
the
user’s
profile
( Prasad
Shinde
)
Should
enter the
user page
or show
incorrect
email,
passwo
rd
Enters
the
user’s
profile
PASS
#3 login 3 Display
s
Home
Web
Layout
1. Click on
the 3
dots on
right
side.
2. Click on
logout
button
from
dropdown
Navigate to user
icon on Nikhil
Thapa’s dashboard
and click on logout
Display
s login
page
Should
display the
homepage
of the app
Button
malfuncti
on
FAIL

4.2 System and Integration Testing
Definition:
Build System testing is a testing level in which tests are performed to know if a
complete aligns with functional and nonfunctional requirements made for it. In
contrast, Integration testing is a testing stage where two or more software units
are joined and tested simultaneously.
Participants: Nikhil Thapa , Prajwal Jadhav
Methodology:
PROJECT NAME: Online Media Player
MODULE/FUNCTIONALITY: Home Page, Audio Player
CREATED BY: Nikhil Thapa
DATE OF REVIEW: 25.11.2021
TEST
CASE
ID
TEST
SCENARIO
TEST
CASE
PRE-
CONDITION
TEST STEPS TEST
DATA
EXPEC
TED
RESU
LT
POST
CONDITION
ACTUAL
RESULT
ST
ATUS
(PASS
/FAIL
)
#1 Home Page 1 Loads Audio,
Video and logout
options
Click on login
option
Loads URL
web page
Displays
home
page
Layout
successfu
lly
Navigate
through home
page
Displays the
required web page
PASS
#2 Audio
Player
4 Loads Audio
Player
Click on the MP3
Music option
Loads
Incognito
Mode
Loads
Audio
Player
Navigate
through Audio
Player
Loads the Audio
Player Successfully
PASS

4.3 Performance and Stress Testing
Definition:
Performance Testing is a type of software testing that is carried out to determine
system performance in terms of sensitivity, reactivity and stability under a
particular workload.
Stress testing is a type of software testing that verifies the stability and reliability
of the system. This test particularly determines the system’s robustness and error
handling under extremely heavy load conditions.
Participants: Nikhil Thapa , Prajwal Jadhav
Methodology:
MODULE/FUNCTIONALITY: Audio Player
CREATED BY: Rohan Mandhare
Web
Page
ID
#
Samples
Average
(secs)
Min (secs)
Max
(secs)
Std.
Dev.
Throughput
SENT
KB/sec
RECVD
KB/sec
Avg.
Bytes
555 11 1 1 1 2.5 30 100 105 102500
213 8 1.5 1 2 1 25 101 103 102000
526 6 1 1 1 0.5 20 102 103 102500

4.4 User Acceptance Testing
Definition:
The purpose of acceptance test is to confirm that the system is ready for
operational use. During acceptance test, end-users (customers) of the system
compare the system to its initial requirements.
Participants: Nikhil Thapa , Rohan Mandhare
Methodology:
MODULE/FUNCTIONALITY: Audio/Video Player
CREATED BY: Bandu Sakhare
TEST
CASE
ID
TEST
SCENARIO
TEST
CASE
PRE-
CONDITION
TEST STEPS
TEST
DATA
EXPECTED
RESULT
POST
CONDITIO
N
ACTUAL
RESULT
ST
ATUS
(PASS
/FAIL
)
#1 Audio
Player
1 Loads Audio
Player
Click on the MP3
Music Button
Navig
ate to
Music
Player
Page
Displa
ys
Music
Payer
successfull
y
Should
click on
the
songs in
the list
Displays
Music
Player
Page
PASS
#2 Video
Player
1 Loads Video
Player
Click on the
Video Player
Button
Navigate
to Video
Player
Displays
Video
Player
Should
click on
the video
Displays Video
Player
Page
PASS
Page successfull songs in
y the list

4.5 Automated Regression Testing
Definition:
Regression testing is the selective retesting of a system or component to verify
that modifications have not caused unintended effects and that the system or
component still works as specified in the requirements.
Participants:
Methodology:
MODULE/FUNCTIONALITY: All
CREATED BY: Nikhil Thapa
ID New Feature Anomaly
#1 Music Effects No
4.6 Beta Testing
Definition:
Beta testing is a type of user acceptance testing where the product team gives a
nearly finished product to a group of target users to evaluate product performance
in the real world.
Participants: Bandu Sakhare , Prajwal Jadhav
Methodology:
CREATED BY: Rohan Mandhare

User
Issues reported
ID
#1 Login Unsuccessful
#2 Delay in opening Video
Player
Features rated
high
Able to navigate
easily between the
audio & video.
Good quality music
and video songs
along with
variations.
Suggestions
Include creation of user’s successful login
Improvement in video Player interface.
4.7 Compatibility Testing:
Definition:
Compatibility Testing is a type of Software testing to check whether your
software is capable of running on different hardware, operating systems,
applications, network environments or Mobile devices.
Participants: Rohan Mandhare , Nikhil Thapa
Methodology:
CREATED BY: Prajwal Jadhav
Hardware
ID Specification
(Processor/Clock
Speed/RAM)
#1 1.8 GHz
#2 8 GB RAM
#3 2.0 GHz
Operating
System
Linux
Windows
10
MacOS
Telecom
Network
Internet WAN
Internet Wi-Fi
Internet Wi-Fi
Browsing
Application
Firefox
Google
Chrome
Apple Safari
Interactive
Testing
(PASS/FAIL)
PASS
PASS
PASS
Comments
None
High speed
High speed
5.0 HARDWARE REQUIREMENTS
The following hardware devices will be required to perform test on the application.
1. Android mobile phone
2. Laptop
3. Wi-Fi (for internet access)

6.0 ENVIRONMENT REQUIREMENTS
 Testing platform: Android Mobile phones
 Database: Google Firebase
 Automated testing tools: Appium, Espresso, Selendroid
 Documentation: TestRail/TestLink
7.0 TEST SCHEDULE
Task Name Start
Date
Finish
Date
Effort
Estimation
Comments
Test Planning 05/10/21 15/10/21 5 d Completed
Review Requirements
documents
15/10/21 18/10/21 3 d Completed
Create initial test estimates 18/10/21 20/10/21 2 d Completed
Staff and train new test
resources
20/10/21 24/10/21 4 d Completed
First deploy to QA test
environment
24/10/21 24/10/21 1 d Completed
Functional testing – Iteration
1
25/10/21 28/10/21 3 d Completed
Iteration 2 deploy to QA test
environment
28/10/21 28/10/21 1 d Completed
Functional testing – Iteration
2
29/10/21 01/11/21 3 d Completed
System testing 02/01/21 07/11/21 5 d Completed
Regression testing 07/07/21 10/11/21 3 d Completed
User Acceptance Testing 07/11/21 10/11/21 4 d Completed
Resolution of final defects
and final build testing
5/11/21 8/11/21 3 d Completed
Deploy to Staging
environment
03/11/21 06/11/21 3 d Completed
Performance testing 05/11/21 10/11/21 6 d Completed
Release to Production 10/11/21 10/11/21 1 d Completed

8.0 Control Procedures:
Problem Reporting
Change Requests
If any changes are to be made in requirements during the testing phase, it willbe
conveyed by the SQA team to the Test Manager. The decision of whether to
include the changes will be decided by the Test manager on the basis of following
criteria:
 The build contains many serious defects which seriously or limit testing
progress.
 Significant change in requirements suggested by client
 Software/Hardware problems

9.0 FEATURES TO BE TESTED
The following features are to be tested:
1. Create Account/Login module
 Create account by providing user information.
 Verify if verification mail is received.
 Check if user can log in by providing ID and password.
2. Home Web Layout
 Search URL
 Browse and navigate through web pages
3. Incognito Mode
 Search required URLs privately
 Browse and navigate through web pages privately
4. App Integrations
 Load other apps and browse through different apps
10.0 FEATURES NOT TO BE TESTED
These features are not be tested because they are not included in the software
requirement specs
 Hardware Interfaces
 Software Interfaces
 Database logical

11.0 RESOURCES/ROLES & RESPONSIBILITIES
Sr.
No.
Rol
e
Members Task
s
1. Test Manager Bandu Sakhare 1. Manage the whole project.
2. Define project directions
2. Tester Rohan
Mandhare ,
Prajwal Jadhav
1. Identifying and describing
appropriate test
techniques/tools/automatio
n architecture.
2. Verify and assess the
Test Approach
3. Execute the test, log results.
4. Report the defects.
3. Test Developer Nikhil Thapa 1. Implement the test cases,
test program, test suite
etc.
2. Builds up and ensures
test environment and
assets are managed and
maintained.
3. Support Tester to use
the test environment for
test execution
4. SQA Members Rohan
Mandhare,
Bandu Sakhare,
Prajwal Jadhav,
Nikhil Thapa
1. Take in charge of
quality assurance.
2. Check to confirm
whether the testing
process is meeting
specified requirements.
12.0 SCHEDULES
Deliverable For Date / Milestone
Test Plan
Project Manager; QA
Director; Test Team
05/10/21
Traceability Matrix
Project Manager; QA
Director
15/10/21
Test Status report
QA Manager, QA
Director
30/10/21
Test Result Report Project Manager 10/11/21

13.0 RISKS/ASSUMPTIONS
The following risks may occur during the mobile app testing process:
 availability of devices
 new features and modification which have not been planned in advance
 changes in requirements
 delays in schedule
The following assumptions have been made for mobile app testing process:
 each release is accompanied by a note with informationabout
implemented features and their impact on the system
 all blocker bugs receive the high priority status
 all the bugs found are fixed before the next softwarerelease
 all documents are up-to-date and delivered to the testing team intime
 all necessary equipment and tools are provided and ready fortesting
 the test schedule is reviewed in case there are any obstacles fortesting
14.0 TOOLS
1. Selenium: An open-source automated testing framework for web application

15.0 APPROVALS
Name Signature Date
1. ROHAN MANDHARE 10/11/21
2. BANDU SAKHARE 10/11/21
3. NIKHIL THAPA 10/11/21
4. PRAJWAL JADHAV 10/11/21
Online Audio Player – TEST CASES

SELENIUM TEST OUTPUT
Project Title: Online Media Player
Group Members:
Rohan Mandhare
Nikhil Thapa
Bandu Sakhare
Prajwal Jadhav

Online Audio Player - STQA_Mini_Project2.pdf

Recommended

Recommended

More Related Content

Similar to Online Audio Player - STQA_Mini_Project2.pdf

Similar to Online Audio Player - STQA_Mini_Project2.pdf (20)

Recently uploaded

Recently uploaded (20)

Online Audio Player - STQA_Mini_Project2.pdf