0% found this document useful (0 votes)
33 views18 pages

Tyco 22518 Ste Microproject2

Uploaded by

jod121609
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
33 views18 pages

Tyco 22518 Ste Microproject2

Uploaded by

jod121609
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 18

A PROJECT

REPORT ON
“TEST CASES FOR HOTSTAR”
SUBMITTED IN PARTIAL FULFILMENT OF THE REQUIREMENTS
FOR THE AWARD OF

DIPLOMA IN
NAME OF THE DEPARTMENT

SUBMITTED TO

MAHARASTRA STATE BOARD OF TECHNICAL


EDUCATION, MUMBAI
SUBMITTED BY

NAME OF THE STUDENT ENROLLMENT NO.


NAME1 0001
NAME2 0002
NAME3 0003
GUIDED BY
Full name of Guide

Made with Campusify! 1


INDEX

Sr Title Page
No. No.
1. Abstract 4

2. Introduction 5

3. Concept 6
4. Test Case Template 7

5 Test Cases 9

5. Conclusion and Reference 15


6. Evaluation Sheet 16

Made with
Abstract
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
and post mortem analysis.

Made with
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.

Testing is important because software bugs could be expensive or even


dangerous. Software bugs can potentially cause monetary and human loss, and
history is full of such examples.

 In April 2015, Bloomberg terminal in London crashed due to software


glitch affected more than 300,000 traders on financial markets. It
forced the government to postpone a 3bn pound debt sale.
 Nissan cars recalled over 1 million cars from the market due to
software failure in the airbag sensory detectors. There has been
reported two accident due to this software failure.
 Starbucks was forced to close about 60 percent of stores in the U.S and
Canada due to software failure in its POS system. At one point, the
store served coffee for free as they were unable to process the
transaction.
 Some of Amazon’s third-party retailers saw their product price is
reduced to 1p due to a software glitch. They were left with heavy losses.
 Vulnerability in Windows 10. This bug enables users to escape
from security sandboxes through a flaw in the win32k system.
 In 2015 fighter plane F-35 fell victim to a software bug, making it
unable to detect targets correctly.
 China Airlines Airbus A300 crashed due to a software bug on April
26, 1994, killing 264 innocents live
 In 1985, Canada’s Therac-25 radiation therapy machine
malfunctioned due to software bug and delivered lethal radiation
doses to patients, leaving 3 people dead and critically injuring 3
others.
M a d e with
 In April of 1999, a software bug caused the failure of a $1.2 b ill i o n
Campusify!
military satellite launch, the costliest accident in history
Concept

In software engineering, a test case is a specification of the inputs, execution


conditions, testing procedure, and expected results that define a single test to be
executed to achieve a particular software testing objective, such as to exercise a
particular program path or to verify compliance with a specific
requirement. Test cases underlie testing that is methodical rather than
haphazard. A battery of test cases can be built to produce the desired coverage
of the software being tested. Formally defined test cases allow the same tests to
be run repeatedly against successive versions of the software, allowing for
effective and consistent regression testing

Formal test cases


In order to fully test that all the requirements of an application are met, there
must be at least two test cases for each requirement: one positive test and one
negative test. If a requirement has sub-requirements, each sub-requirement
must have at least two test cases. Keeping track of the link between the
requirement and the test is frequently done using a traceability matrix. Written
test cases should include a description of the functionality to be tested, and the
preparation required to ensure that the test can be conducted.
A formal written test case is characterized by a known input and by an expected
output, which is worked out before the test is executed. The known input should
test a precondition and the expected output should test a post condition.

Informal test cases


For applications or systems without formal requirements, test cases can be
written based on the accepted normal operation of programs of a similar class.
In some schools of testing, test cases are not written at all but the activities
and results are reported after the tests have been run.
In scenario testing hypothetical stories are used to help the tester think through
a complex problem or system. These scenarios are usually not written down in
any detail. They can be as simple as a diagram for a testing environment or they
could be a description written in prose. The ideal scenario test is a story that is
motivating, credible, complex, and easy to evaluate. They are usually different
from test cases in that test cases are single steps while scenarios cover a number
of steps of the key.

Made with Campusify!


Test Case Template
Test Case
Field Test case Description
ID:  Each test case should be represented by a
unique ID. To indicate test types follow
some convention like “TC_UI_1” indicating
“User Interface Test Case#1.”

 It is useful while executing the test.


Test Priority:
 Low
 Medium
 High

 Determine the name of the main module


Name of the Module:
or sub-module being tested

 Tester’s Name
Test Designed by:
 Date when test was designed
Date of test
 Who executed the test- tester
designed: Test
 Date when test needs to be executed
Executed by:
 Title of the test case
Date of the
Test Execution:  Determine the summary or test purpose
Name or Test Title: in brief

Description/Summary  Any requirement that needs to be done before


of Test: execution of this test case. To execute this
test case list all pre-conditions
Pre-condition:
 Determine any dependencies on
test requirements or other test cases

Dependencies:  Mention all the test steps in detail and write


in the order in which it requires to be
executed. While writing test steps ensure that
Test Steps: you provide as much detail as you can
Made with Campusify!
Test Data:  Use of test data as an input for the test case.
7
Computer Department

Made with Campusify!


Deliver different data sets with precise values
to be used as an input

Expected Results:  Mention the expected result including error


or message that should appear on screen

Post-Condition:  What would be the state of the system


after running the test case?

Actual Result:  After test execution, actual test result


should be filled

Status (Fail/Pass):  Mark this field as failed, if actual result is


not as per the estimated result

Notes:  If there are some special condition which


is left in above field

Made with Cam8


Computer
Test Cases
Test Cases for
Hotstar

Test Pre- Test Case Input Case Expected Actual Result Status
Case requisites Result
No
1 Hotstar Verifying the Turning on Login page Login page Pass
Application application has the is is
is ON login page application displayed displayed
and waiting
for login
page
2 Hotstar Verify that the Turning on User should The text is Pass
Application text on the the be able to readable and
is ON mobile app is application view and clear
readable and waiting read the text
and clear. for text to clearly
display
3 Hotstar Verifying that on Video for Video Video started Pass
Application cliking the video testing should start playing when
is ON play icon over playing play icon was
the video, the when play clicked
video should icon is
play. clicked

4 Hotstar Verify all the video Video for When All controls Pass
Application player controls- testing clicked on worked as
is ON play, pause, play video expected
volume, mute etc. should start
playing,
pause to
pause video
volume to
increase or
decrease
volume and
mute to off
audio
5 Hotstar Verify that user Video for User should User was able Pass
Application can select the testing be able to to change the
is ON allowed video change quality of
quality for quality of video
playing the video. video

6 Hotstar Verify that Video for User should User was able Pass
Application once the testing be able to to replay video

Computer
video is

Made with Cam9 pusify!

Computer
is ON complete, user replay video using replay
can replay the using replay icon
video using icon once
‘replay’ icon. video is
finished
7 Hotstar Verify that video Videos user Once user Relevant Pass
Application should be want to types name videos of
is ON searchable by search in search bar given name
name, displaying relevant was displayed
the most relevant videos of
video on the top given name
in search results. should be
displayed

8 Hotstar Verify that other Videos user User should User was able Pass
Application attributes of video want to be able to to search video
is ON like artist name, search search video by typing
description by typing artist name
should also be artist name and
searchable and description
description

9 Hotstar Verify that with Video for View count View count Pass
Application each view the testing should was increase
is ON ‘view count’ increase by by one with
increases by one with each view
one. each view
10 Hotstar Verify that the Video for The related The related Pass
Application related videos are testing videos videos were
is ON related to the should be related to the
current video or related to current video
is based on the the current or based on
past viewing video or the past
history of user. based on viewing history
the past of user
viewing
history of
user

11 Hotstar Verify that clicking Video for Video Video was Pass
Application related video testing should open opened when
is ON thumbnail should when clicked clicked on
open the video. on thumbnail.
thumbnail.

Made with C1am0


Computer
12 Hotstar Verify that every Video for Every video Every video Pass
Application video viewed goes testing viewed viewed went
is ON to history for should go to history for
logged in user. to history logged in user.
for logged
in user.

13 Hotstar Verify that user Video for User should User was able Pass
Application can view or delete testing be able to to view or
is ON history items. view or delete history
delete items
history
items

14 Hotstar Verify that the app Recieveing The App The app is Pass
Application goes into the Call while should run running in
is ON background when app is in background
on call. running background
without any
disturbance
15 Hotstar Verify that the app Receiveing The App The app is Pass
Application still operates as Message should run running in
is ON designed when a while app is in background
message or running background
notification pop-up without any
from another app disturbance
such as Facebook
messaged,
Instagram, etc.

16 Hotstar Check Internet for The Change in Pass


Application the Performance o testing performance performance
is ON f the app on the changes
different internet when the
networks such as internet
1G, 2G, 3G, or 4 G network is
networks. changed

Made with C1am1


Computer
17 Hotstar Check that Combability Runs on Runs on Pass
Application the app is check on different different
is ON adaptable different devices devices
to different device
mobile platforms
or OS such as
Android, iOS,
Microsoft, etc.

18 Hotstar Verify that the optimization Run Run smoothly Pass


Application loading time for Check on the smoothly on on different
is ON the app is not too device different devices
long. devices

19 Hotstar Check that The app The app The app runs Pass
Application the app is should run runs successfully
is ON still working after the successfully after the
as update after the update
intended after the update
successful update
of the app.

20 Hotstar Check how Running the App should App should Pass
Application the app function app on run properly run properly
is ON under different different on different on different
battery levels and battery levels battery level battery level
temperatures.

21 Hotstar Verify that the Running the The app is The app is Pass
Application app is not app for 2 not draining not draining
is ON draining too hours too much too much
much battery. battery battery

22 Hotstar Check that logging out Unable to Unable to Pass


Application the app does not before the logout logout
is ON log end of a
out the user session
before the end
of a session.
23 Hotstar To ensure that Tapping for Able to Able to zoom- Pass
Application the validation for zoom-in and zoom-in and in and zoom-
is ON the tapping zoom-out zoom-out out
zoom-in and
zoom-out
facilities should
be enabled.

Made with C1am2


Computer
24 Hotstar Does the app Trying to does does support Pass
Application support payment do support payment
is ON gateway payment payment gateway
transactions? gateway transaction
transaction

25 Hotstar Are page Trying to Able to Able to scroll Pass


Application scrolling scroll while scroll while while running
is ON scenarios running the running the the app
working as app app
expected?
26 Hotstar Can the app Trying, Able to Able to handle Pass
Application handle projected projected handle projected load
is ON load volumes? load volume projected volume
load volume
27 Hotstar Buttons Checking the Easy to Easy to access Pass
Application location, style, location/style access the the button
is ON etc are of button button and and are stylish
consistent within are stylish
the app.
28 Hotstar The keyboard Trying to Able to Able to Pass
Application can be minimized minimized minimized minimized and
is ON and maximized and and maximized the
easily. maximized maximized keyboard
the keyboard the
keyboard

29 Hotstar Going back, touching the Able to Able to Pass


Application undoing an wrong item undone the undone the
is ON action, or on that can be item easily item easily
touching the easily be
wrong item can undone.
easily be undone.

30 Hotstar Time and checking the Able to view Able to view Pass
Application date are time and correct time correct time
is ON properly date in the and date and date
formatted. app accordinly to accordinly to
region region selected
selected

Made with C1am3


Computer
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

Reference
 https://sampletestcases.com/test-cases-for-
Hotstar/
 https://www.softwaretestingo.com/Hotstar-

test-cases/
 https://artoftesting.com/test-scenario-examples

Made with C1am4


Computer
Title of Project: Prepare test cases for Hotstar

1. Aims/Benefits of the Micro-Project:


a) Great help with studies and in making a career choice.
b) Improves academic performance and interest.
c) To Support Self Directed Learning. d) To help students
develop teamwork and problem-solving skills.
e) To enhance the skills to ‘communicate effectively and skilfully at
workplace’.

2. Course Outcomes Addressed:


a) Apply various software testing skills and method.
b) Prepare test cases for different levels and types testing.
c) Prepare test plan for an application.
d) Identify bugs to create defect report.
e) Test software for performance measures using automated tools.

3. Proposed Methodology:
The work is assigned to 1 student. To complete the Project “Test cases
for Hotstar”, qualitative method will be used in which data collection,
analysis and interpretation is required. The data will be collected from
different sources such as Internet, reference books etc. The analysis and
interpretation will be done by observing the collected data &
programming work. Finally the data will be represented with
interpretation in the form of application or collected data.

Made with C1am5


Computer
4. Action Plan:
Sr.n Details of Activity Planned Planned Name of
Start date Finish date Responsible
o
Team
Members
1 Discussion and
Finalization of the
Project
Title
2 Preparation of Abstracts
3 Literature Review
4 Collection of Data
5 Discussion and Outline of
Content
6 Rough Writing of the
Projects Contents
7 Editing and Proof
Reading of the Contents
8 Final Completion of the
Project
9 Seminar Presentation,
viva vice,
Assessment
and Submission of Report

5. Resources Required:
Sr.no. Name of Specifications Qty. Remarks
resource
/material
1 Computers HP430 1
2 Open learning Internet 1
sources

Made with C1am6


Computer

You might also like