Test Cases For Telegram

Program Name and Code: CO5I Academic Year : 2021-22

Course Name and Code: Software Testing (22518) Semester : Fifth

A STUDY ON

Test Cases for Telegram

MICRO PROJECT
Submitted in Feb. 2021 by the student

Sr. Roll No Enrollment Seat No

Full name of Student
No (Sem-V) No (Sem-V)
1 56 Sahil Sanjay Narale 1917340079

Under the Guidance of

Prof. Mohite.S.S
in

Three Years Diploma Programme in Engineering & Technology of Maharashtra State Board
of Technical Education, Mumbai (Autonomous)
ISO 9001:2008 (ISO/IEC-27001:2013)

at

1734 – TRINITY POLYTECHNIC PUNE

1
Test Cases For Telegram

MAHARASHTRA STATE BOARD OF TECHNICAL

EDUCATION, MUMBAI

Certificate

This is to certify that Mr. / Ms.

Roll No: of Fifth Semester of Diploma

Programme in Engineering & Technology at 1734 – Trinity Polytechnic Pune, has

completed the Micro Project satisfactorily in Subject ______________in the academic year

2021-22 as per the MSBTE prescribed curriculum of I Scheme.

Place: Pune Enrollment No:

Date : / / 2021 Exam. Seat No:

Project Guide Head of the Department Principal

Seal of Institute

2
 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

Abstract

3
Computer Department
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

4
Computer Department
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.
 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

5
Computer Department
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.

6
Computer Department
  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  Determine the summary or test purpose in

of 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-conditions

Dependencies:  Determine any dependencies on test

requirements or other test cases

Test Steps:  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
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

7
Computer Department
 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

Test Cases
Test Cases for Telegram

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

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

6 Hotstar Verify that once the Video for User should User was able Pass
Application video is complete, testing be able to to replay
is ON user can replay the replay video video using
video using ‘replay’ using replay replay icon
icon. icon once
video is
finished

9
Computer Department
 7 Hotstar Verify that video Videos user Once user Relevant Pass
Application should be searchable want to search types name videos of
is ON by name, displaying in search bar given name
the most relevant relevant was displayed
video on the top in videos of
search results. given name
should be
displayed

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

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

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

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

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

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

16 Hotstar Check Internet for The Change in Pass

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

17 Hotstar Check that the Combability Runs on Runs on Pass

Application app is adaptable to check on different different
is ON different mobile different devices devices
platforms or OS device
such as Android,
iOS, Microsoft,
etc.

18 Hotstar Verify that the optimization Run smoothly Run smoothly Pass
Application loading time for Check on the on different on different
is ON the app is not too device devices devices
long.

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

20 Hotstar Check how the Running the App should App should Pass
Application app function under app on run properly run properly
is ON different battery different on different on different
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 draining app for 2 not draining not draining
is ON too much battery. hours too much too much
battery battery

22 Hotstar Check that the logging out Unable to Unable to Pass

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

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

25 Hotstar Are page Trying to scroll Able to scroll Able to scroll Pass
Application scrolling scenarios while running while running while running
is ON working as the app the app the app
expected?

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

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

12
Computer Department
 27 Hotstar Buttons location, Checking the Easy to Easy to Pass
Application style, etc are location/style access the access the
is ON consistent within of button button and button and
the app. are stylish are stylish

28 Hotstar The keyboard Trying to Able to Able to Pass

Application can be minimized minimized and minimized minimized
is ON and maximized maximized the and and
easily. keyboard maximized maximized
the keyboard the keyboard

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

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

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

Conclusion

Thus I have prepared test cases for Telgram. 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

13
Computer Department
 Reference
 https://sampletestcases.com/test-cases-for-
Hotstar/
 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 Addressed:
14
Computer Department
 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.

4. Action Plan:
Sr.no Details of Activity Planned Planned Name of
Start date Finish date Responsible
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

15
Computer Department
 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

Name of student: Sahil Sanjay Narale

Roll no: 56
Name and Signature of the Teacher

16
Computer Department