Sr Title Page No.

No.
1 Abstract
2 Introduction
3 Concept
4 Test case Template
5 Test Cases
6 Conclusion and Reference
7 Evolution Sheet
INDEX
 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.
 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 Ip 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.

In April of 1999, a software bug caused the failure of a $1.2 billion

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.
 Test Case Template
Irrespective of the test case documentation method chosen, any
good test case template must have the following fields

Test Case Field Description

Test case 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."
Test Priority: It is useful while executing the test.
Low

Medium

High

Name of the Module: • Determine the name of the main module or

sub-module being tested

Test Designed by: Tester's Name

Date of test designed: Date when test was designed

Test Executed by: Who executed the test-tester?

Date of the Test Date when test needs to be executed

Execution:

Name or Test Title: Title of the test case

Description/Summary of Determine the summary or test purpose in

Test: brief

Pre-condition: Any requirement that needs to be done

 before execution of this test case. To execute
this test case, list all pre-condition
Dependencies: Determine any dependencies on test
requirements or other test cases
Test Steps: Mention all the steps in detail and write in the
order in which it requires to be executed.
While writing test step ensure that you
provide as much detail as you can
Test Data: Use of test data as an input for the test case.
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 above field

Test Cases

Test Cases for Telegram

Test Prerequisites Test Case Input case Expected Actual Result Status
case Result
no.
1 Hotstar Verifying the Turning on Login page is Login page is Pass
Application is application the displayed displayed
ON has login page application
and writing
for login
page
2 Hotstar Verify that Turning on User should be The test is Pass
 Application is the text on the able to view readable and
ON the mobile application and read the clear
and clear and waiting text clearly
for text to
display
3 Hotstar Verify all the Video for Video should Video started Pass
Application is video player testing start playing playing when
ON controls- play, when play icon play icon was
pause, is clicked clicked
volume, must
etc.
4 Hotstar Verifying all Video for When clicked All controls Pass
Application is the video testing on play video worked as
ON player should start expected
control-play, playing, pause
pause, to pause video
volume, mute volume to
etc increase or
decrease
volume and
must to off
audio
5 Hotstar Verify that Video for User should be User was able Pass
Application is user can testing able to change to change the
ON select the quality of quality of
allowed video video video
quality for
playing the
video
6 Hotstar Verify that Video for User should be User was able Pass
Application is once the testing able to replay to replay video
ON video is video using using relay
complete, replay icon icon
user can once video is
replay the finished
video using
‘replay’
7 Hotstar Verify that Video user Once user Relevant Pass
Application is video should want to types name in videos of given
ON be searchable search search bar name were
by name, relevant video displayed
displaying the of given name
most relevant should be
video on the displayed
top in search
results
8 Hotstar Verify that Video user User should be User was able Pass
Application is other want to able to search to search video
ON attributes of search video by typing by typing artist
video like artist name name and
artist name, and description
 description description
should also
searchable
9 Hotstar Verify that Video for View count View count Pass
Application is with each testing should was increase
ON view the increase by by one with
‘view count’ one with each each view
increase by view
one
10 Hotstar Verify that Video for The related The related Pass
Application is the related testing video should video was
ON video is be related to related to the
related the the current current video
current video video or based or based on
or is based on on the past the past
the past viewing history viewing history
viewing of user of user
history of
user
11 Hotstar Ing related Video for Video should Video was Pass
Application is video testing open when opened when
ON thumbnail clicked on clicked
should open thumbnail thumbnail
the video
12 Hotstar Verify that Video for Every video Every video Pass
Application is every video testing viewed should viewed want
ON viewed goes go to history to history for
to history for for logged in logged in user
logged in user user
13 Hotstar Verify that Video for User should be User was able Pass
Application is user can view testing able to view or to view or
ON or deleted delete history delete history
history items items items
14 Hotstar Verify that Receiving The app should The app is Pass
Application is the app goes Call while run in running in
ON into the app is background background
background running
when on call
15 Hotstar Verify that Receiving The app should The app is Pass
Application is the app still Message run in running in
ON operates as while app is background background
designed running without any
when a disturbance
message or
notification
pop-up from
another app
such as
Facebook
messaged,
Instagram,
 etc.
16 Hotstar Check the Internet for The Change in Pass
Application is Performance testing performance performance
ON of the app on changes when
the different the internet
internet network is
network such changed
as 1G, 2G, 3G
or 4G
networks
17 Hotstar Check that Combability Runs on Runs on Pass
Application is the app is check on different different
ON adaptable to different devices devices
different device
mobile
platforms or
so such as
Android, iOS,
Microsoft,
etc.
18 Hotstar Verify that Optimization Run smoothly Run smoothly Pass
Application is the loading Check on the on different on different
ON time for the device devices devices
app is not too
long.
19 Hotstar Check that The app The app runs The app runs Pass
Application is the app is still should run successfully successfully
ON working as after the after the after the
intended after update update update
the successful
update of the
app
20 Hotstar Check how Running the App should run App should Pass
Application is the app app on properly on Pass run
ON function different different properly on
under battery levels battery level different
different battery level
battery levels
and
temperatures.

21 Hotstar Verify that Running the The app is not he app is not Pass
Application is the app is not app for 2 draining too draining too
ON draining too hours much battery much battery
much battery.
22 Hotstar Check that logging out Unable to Unable to Pass
Application is the app does before the logout logout
ON not log out end of a
the user session
before the
end of a
 session.
23 Hotstar o ensures that Tapping for Able to zoom- Able to zoom- Pass
Application is the validation zoom-in and in and zoom- in and zoom-
ON for the zoom-out out out
tapping
zoom- in and
zoom-out
facilities
should be
enabled.

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

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

Application is scrolling scroll while while running Pass while
ON scenarios running the the app running the
working as app app
expected?

26 Hotstar the app Trying, Able to handle Able to handle Pass

Application is handle projected projected load projected load
ON projected load volume volume volume
load
volumes?

27 Hotstar Buttons Checking the Easy to access Easy to access Pass

Application is location, location/style the button and the button and
ON style, etc are of button are stylish are stylish
consistent
within the
app.

28 Hotstar The keyboard Trying to Able to Able to Pass

Application is can be minimized minimized and minimized and
ON minimized and maximized the maximized the
and maximized keyboard keyboard
maximized the keyboard
easily.
29 Hotstar Going back, Time and Able to Able to Pass
Application is undoing an date are undone the undone the
ON action, or on properly item easily item easily
touching the formatted.
wrong item
can easily be
undone.

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

Conclusion
Thus, I have prepared test cases for telegram. 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://www.softwaretestingo.com/Hotstar- test-cases/
https://artoftesting.com/test-scenario-examples

Title of Project: Prepare test cases for Telegram

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 Addressee

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 Telegram", 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.67