Program Name and Code: CW5I A.

Y 2024-25
Course Name and Code: SOFTWARE TESTING (22518) Semester: V

A Study On
TEST CASES FOR TELEGRAM
MICRO PROJECT
Submi ed in Academic Year 2024-25 BY the Student

SR.NO ROLL NO FULL NAME ENROLLMENT SEAT NO

1 2210050072 SHAIKH SAHIM SHARIF 2210050072

Under The Guidance Of

MRS. PRATIBHA WARKHED
In
Three Years Diploma Program in Engineering and Technology of Maharashtra
State Board of Technical Educa on (MSBTE)
At
SBNM POLYTECHNIC, GEORAI TANDA,
CH. SAMBHAJINAGAR.
 MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION

Certificate

This is to certify that Mr. Shaikh Sahim Sharif Roll No. 2210050072 of 5TH
Semester of Diploma in Computer Science and Engineering of Institute,
SBNM POLYTECHNIC (Code: 1005) has completed the Micro Project
satisfactorily in Subject – STE (22518) for the academic year 2024 - 2025 as
prescribed in the curriculum.

Place: Ch. Sambhajinagar Enrollment no: 2210050072

Date: ……………………… Exam. Seat No:

Subject Teacher HOD Principal

Seal of
Ins tute
 ACKNOWLEDGEMENT

I take this opportunity to express deep sense of gratitude and sincere thanks
for the invaluable guidance that I have received at the worthy hands of my guide
MRS. PRATIBHA WARKHED.
I express my sincere thanks to our H.O.D. MR. RAVI TANGADE for
permitting me to do this project and also to the entire staff member who have
helped me directly or indirectly.
I also express my thanks to my friends for their underlying support shown
during the preparation of this project.

_______________________

DEPARTMENT OF COMPUTER ENGINEERING

SBNM POLYTECHNIC, GEORAI TANDA,
CH. SAMBHAJINAGAR, 431002.
 INDEX

REPORT PART (A)

Sr. no. Content Page no.

1. Abstract 1

2. Introduc on 2

3. Concept 3

REPORT PART (B)

1. Aim of Microproject 4

2. Course Outcome Addressed -||-

3. Proposed Methodology -||-

4. Ac on Plan 5

5. Resources Required 6

REPORT PART (C)

1. Test Case Template 7-8

2. Test Cases for Telegram 9-16

3. Conclusion 17

4. Evalua on Sheet 18
 PART (A)

1.0: 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.

1
2.0: 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.

2
3.0: 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.

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.

3
 PART (B)

1.0: AIM OF MICROPROJECT:

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 student develop teamwork and problem-solving skills
E. To enhance the skills to ‘communicate effectively and skilfully at workplace’

2.0: COURSE OUTCOMES ADDRESSED:

A. Apply various software testing skills and method.
B. Prepare test cases for different level 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.0: PROPOSED METHODOLOGY:

The work is assigned to 1 student. To complete the project “Test case 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
book 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
or collected data.

4
4.0: ACTION PLAN:

Planned Planned
Name of
Sr.no Details of Ac vity Start Finish
Responsibili es
date date
Discuss and Finaliza on of
1
the Project tle
2 Prepara on of abstracts

3 Literature review

4 Collec on of data

Discuss and Outline of

5
content
Rough Wri ng of the Projects
6
Content
Edi ng and Proof Reading of
7
Content
Final Comple on of the
8
Project
Seminar Presenta on, viva
9 vice, Assessment and
Submission of Report

Name and Signature of Faculty

5
5.0: RESOURCES REQUIRED:

Sr. No Name of Specifica on Qty. Remarks

Resource/Material

1 Computers HP430 1

2 Open Learning Internet 1

Sources

(To be approved by concerned Teacher)

6
1.0 TEST CASE TEMPLATE

Test Case Field Descrip on

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 Test Execu on: Date when test needs to be executed

Name or Test Title: Title of the test case

Descrip on/Summary Determine the summary or test purpose in brief

of Test:

7
Pre-condi on: 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-Condi on: 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: Mark this field as failed, if actual result is not as per the
estimated result

Notes: If there was are some special conditions which is left in

above field

8
2.0 TEST CASE FOR TELEGRAM

Test Pre- Test Case Input Case Expected Result Actual Status
Case requisites Descrip on Result
No.

1 Hotstar Verifying the Turning on Login page is Login page Pass

Application application the displayed is displayed
is ON has login page application
and waiting
for login
page
2 Hotstar Verify that the Turning on User should be The text is Pass
Application text on the the able to view readable
is ON mobile app is application and read the and clear
readable and and waiting text clearly
clear. for text to
display
3 Hotstar Verifying that Video for Video should Video Pass
Application on clicking the testing start playing started
is ON video play when play icon playing
icon over the is clicked when play
video, the icon was
video should clicked
play.
4 Hotstar Verify all the Video for When clicked All Pass
Application video player testing on play, video controls
is ON controls- play, should start worked as
pause, playing, pause expected
volume, mute, to pause video,
etc. volume to
increase or
decrease, mute
to off audio

9
Test Pre- Test Case Input Expected Result Actual Result Status
Case requisites Descrip on Case
No.

5 Hotstar Verify that user Video User should be User was able Pass
Application can select the for able to change to change the
is ON allowed video testing the quality of quality of
quality for video video
playing the
video.

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

7 Hotstar Verify that video Videos Once user Relevant Pass

Application should be user types name in videos of
is ON searchable by wants to search bar, given name
name, displaying search relevant videos were
the most of given name displayed
relevant video should be
on the top in displayed
search results.

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

10
Test Pre- Test Case Input Expected Result Actual Result Status
Case requisites Descrip on Case
No.

9 Hotstar Verify that with Video View count View count Pass
Application each view, the for should increase increased by
is ON 'view count' testing by one with one with each
increases by one. each view view

10 Hotstar Verify that the Video The related Related videos Pass
Application related videos are for videos should were relevant
is ON related to the testing be related to the to the current
current video or current video or video or past
based on the past based on past viewing
viewing history of viewing history history
the user. of user

11 Hotstar Verify that Video Video should Video was Pass

Application clicking related for open when opened when
is ON video thumbnail testing clicked on clicked on
should open the thumbnail thumbnail
video.

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

11
Test Pre- Test Case Input Case Expected Actual Result Status
Case requisites Descrip on Result
No.

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

14 Hotstar Verify that the Receiving The app The app is Pass
Application app goes into call while should run in running in
is ON the background app is the background
when on call. running background
without any
disturbance
15 Hotstar Verify that the Receiving The app The app is Pass
Application app still message should run in running in
is ON operates as while app the background
designed when a is running background
message or without any
notification pop- disturbance
up from another
app such as
Facebook,
Instagram, etc.
16 Hotstar Check the Internet The Change in Pass
Application performance of for testing performance performance
is ON the app on changes when
different the internet
internet network is
networks such changed
as 1G, 2G, 3G,
or 4G networks.

12
Test Pre- Test Case Input Case Expected Actual Status
Case requisites Descrip on Result Result
No.

17 Hotstar Check the Runs on Runs on Runs on Pass

Application compatibility
is ON

18 Hotstar Verify that the Optimization Run Run Pass

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

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

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

13
Test Pre- Test Case Input Case Expected Actual Result Status
Case requisites Descrip on Result
No.

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

22 Hotstar Check that the Logging Unable to log Unable to log Pass
Application app does not log out before out out
is ON out the user the end of
before the end of a session
a session.

23 Hotstar Ensure that the Tapping Able to Able to Pass

Application validation for for zoom- zoom in and zoom in and
is ON tapping zoom-in in and zoom out zoom out
and zoom-out zoom-out
facilities is
enabled.

24 Hotstar Does the app Trying to Supports Supports Pass

Application support payment do payment payment
is ON gateway payment gateway gateway
transactions? transactions transactions

14
Test Pre- Test Case Input Case Expected Actual Status
Case requisites Descrip on Result Result
No.

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

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

26 Hotstar Can the app Trying Able to Able to Pass

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

27 Hotstar Buttons Checking the Easy to Easy to Pass

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

28 Hotstar The keyboard Trying to Able to Able to Pass

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

15
Test Pre- Test Case Input Case Expected Actual Result Status
Case requisites Descrip on Result
No.

29 Hotstar Going back, Touching Able to Able to Pass

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

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

16
3.0 COCLUSION:
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

ELECTRONIC RESOURCES:

https://sampletestcases.com/test-cases-for- Hotstar/
https://www.softwaretestingo.com/Hotstar- test-cases/
https://artoftesting.com/test-scenario-examples/

TITLE OF THE MIRCOPROJECT:

 PREPARE TEST CASES FOR TELEGRAM

17
 DEPARTMENT OF COMPUTER SCIENCE AND ENGINEERING

Name of Student: SHAIKH SAHIM SHARIF Enrollment No: 2210050072

Course Title: STE Code: 22518

Name of Program: COMPUTER SCIENCE & ENG. Semester: V

Title of Micro Project: PREPARING TEST CASES FOR TELEGRAM

4.0 MICRO PROJECT EVALUATION SHEET

(A) (B)
Process and Product Individual Presenta on /
Total Marks 10
Assessment (6 Marks) Viva (4 Marks)

Comments/Sugges ons about team work/leadership/inter-personal

communica on (if any)

_________________________________________________________________
_________________________________________________________________
_______________________

Any other Comments:

_________________________________________________________________
_________________________________________________________________
_______________________

Name and Designa on of Faculty Members: MRS. PRATIBHA WARKHED

Signature:

18