Diploma Course in Computer Engineering
(As per directives of I Scheme, MSBTE)
SUBJECT : SOFTWARE TESTING
SUBJECT CODE : 22518
AIM : ‘ Preparation of Test Cases for Hotstar ’
ACADEMIC YEAR : 2024 - 25
ROLL NO. NAME BRANCH
3132 KUSHAL PATIL
3133 ANIKET SHARMA
CO5I
3140 SHREELESH PAWAR
3172 KRRISH PATIL
Under Guidance of –
Mrs.Kavita Mam
PART A – PLAN
TOPIC OF THE MIRO-PROJECT : “Preparation of Test
Cases for Hotstar”
❖ BRIEF INTRODUCTION: A test case is a detailed
document that specifies a set of conditions or variables
to determine whether a software application functions
correctly. Test cases for Hotstar are structured scenarios
designed to validate the platform's functionality,
performance, and user experience. These Test Cases help
to ensure that Hotstar delivers a seamless and enjoyable
user experience, addressing functionality, security, and
performance needs effectively.
❖ AIM OF THE MICRO-PROJECT :
● The main aim of the Micro-Project is to design the Test
Cases for the Hotstar.
● Identifying Key Features : Understanding the core
functionalities of Hotstar, such as user registration,
content streaming, search capabilities, and payment
processing.
● Performance Testing : Assessing how the application
performs under different load conditions, ensuring it can
handle peak usage without issues.
❖ ACTION PLAN-
SR DETAIL OF ACTIVITY PLAN START PLAN END NAME OF MEMBERS
NO. DATE DATE
1. Group was formed 15/07/24 26/07/24 KUSHAL PATIL
according to the Roll no. ANIKET SHARMA
and Group leader was SHREELESH PAWAR
selected. KRRISH PATIL
2. Finalization of micro 29/07/24 09/08/24 KUSHAL PATIL
project and discussion of SHREELESH
Micro project. PAWAR
KRRISH PATIL
3. Planning of micro project 12/08/24 23/08/24 KUSHAL PATIL
regarding resources, ANIKET SHARMA
language used, software SHREELESH PAWAR
used, submission date,
completing Part A plan of
Project.
4. Complete analysis and 26/08/24 06/09/24 KUSHAL PATIL
Design part of Micro ANIKET SHARMA
project and distribution KRRISH PATIL
of module among group
members.
5. Designing Commands for 09/08/24 20/09/24 KUSHAL PATIL
project and getting it KRRISH PATIL
finalized from guide.
6. Presentation of micro- 23/09/24 04/10/24 KUSHAL PATIL
project in front of Guide ANIKET SHARMA
by each member of group SHREELESH PAWAR
and preparing Part B plan KRRISH PATIL
for micro-project.
7. Submission of Micro- 07/10/24 11/10/24 All Members
project both Plan A & B,
hard copy.
❖ RESOURCES REQUIRED-
SR NO. NAME OF SPECIFICATIONS QTY REMARKS
RESOURCE
1. CHROME Referring 1
[websites] various
websites for
gathering
information
2. Computer Co- 1
Processor-
intel core 2
dual CPU
E6550
3. Open Learning Internet
Sources
PART B – PLAN
TOPIC OF THE MIRO-PROJECT : “Preparation of Test Cases
for Hotstar”
❖ BRIEF INTRODUCTION : This Micro-project focuses on
designing comprehensive test cases for the Hotstar streaming
platform to ensure its reliability, performance, and user
satisfaction. By identifying key features such as user
registration, content playback, and payment processing, we
will create test scenarios that cover a variety of conditions,
including usability, security, and compatibility across devices.
The goal is to enhance the overall user experience, verify
compliance with industry standards, and identify areas for
improvement, ultimately contributing to a seamless and
enjoyable viewing experience for users.
❖ AIM OF THE MICRO-PROJECT :
● The aim of the Micro project is to design test cases for
Hotstar would be to ensure the platform’s functionality,
usability, and performance meet user expectations and
technical specifications.
● Creating Test Cases : Developing detailed test cases that
cover various scenarios, including positive, negative,
boundary, and edge cases. This ensures comprehensive
testing of each feature.
❖ COURSE OUTCOME INTEGRATED :
a) Apply various software testing skills and method.
b) Prepare test cases for different levels and types
of Software Testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report.
e) Test software for performance measures using
automated tools.
❖ Actual Procedure Followed:
1) Groups are made according to the roll number
and Branch.
2) Arranged a meeting and discussed the STE
Microproject.
3) Gathered information about the Microproject.
4) Gathered resources required for the Microproject.
5) Gathered more information related to
the Microproject.
6) Gathered more resources related to the
Microproject.
7) Submitted The Hardcopy of The Microproject
after Completion.
REPORT
❖ DESCRIPTION:
Software Testing is a process, which involves, executing of a
software program/application and finding all errors or bugs in that
program/application so that the result will be a defect-free software.
Quality of any software can only be known through means of testing
(software testing). Through the advancement of technology around
the world, there increased the number of verification techniques
and methods to test the software before it goes to production and
off course to market. Automation Testing has made its impact in the
testing process. Now-a-days, most of the software testing is done
with the automation tools which not only lessens the number of
people working around that software but also the errors that can be
escaped through the eyes of the tester. Automation testing contains
test cases which makes the work easy to capture different scenarios
and store them. Therefore, software automation testing process
plays a vital role in the software testing success. This study aims in
knowing different types of software testing, software testing
techniques and tools and to compare manual testing versus
automation testing.
The development of large software systems is a complex and error
prone process. Faults might occur at any development stage and
they must be identified and removed as early as possible to stop
their propagation and reduce verification costs. Quality engineers
must be involved in the development process since the very early
phases to identify required qualities and estimate their impact on
the development process. Their tasks span over the whole
development cycle and go beyond the product deployment through
maintenance & post mortem analysis.
❖ Introduction :
● Software Testing is a method to check whether
the actual software product matches expected
requirements and to ensure that software
product is Defect free. It involves execution of
software/system components using manual or
automated tools to evaluate one or more
properties of interest. The purpose of software
testing is to identify errors, gaps or missing
requirements in contrast to actual
requirements.
● Software Testing is Important because if there
are any bugs or errors in the software, it can be
identified early and can be solved before
delivery of the software product. Properly
tested software product ensures reliability,
security and high performance which further
results in time saving, cost effectiveness and
customer satisfaction
Test Case Template
Irrespective of the test case documentation method chosen,
any good test case template must have the following fields
Test Cases
Test cases for Hotstar
Test Cases
Test Cases for Hotstar
Conclusion
Thus I have prepared test cases for Hotstar. I have
successfully executed the thirty test cases. Thus,
Software Testing is Important because if there are
any bugs or errors in the software, it can be
identified early and can be solved before delivery
of the Software product.
