MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION
VIDYAVARDHINI’S BHAUSAHEB VARTAK
POLYTECHNIC, VASAI ROAD WEST
MICRO PROJECT
Academic year: 2024-25
Title of Micro Project:
Movie Ticket Booking System
Program/Code: Computer Engineering (CO) Semester: FIFTH
Course/Code: Software Testing (22518)
Name:
PRANJAL TAMULI
RUTUJA VAIDYA
REYAN DABRE Roll.No:1858,1859,1860
Enrollment No. : 2200930176,2200930178,2200930181
Name of Faculty: Mrs. Seema Kaimal
MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION
Certificate
This is to certify that Mr. /Ms. …………………………………………………………..
Roll No ……….. of Fifth Semester of Diploma in Computer Engineering- I ( CO-5-I)
of Institute , B.V. POLYTECHNIC (Code: 0093) has completed the Microproject
satisfactorily in Subject –Software Testing (22518) for the academic year 2024- 2025
as prescribed in the curriculum.
Place: Vasai Enrollment No: … … … … … … … … … … …
Date: ……………………… Examination Seat No: …………………………………….
Subject Teacher Head of the Department Principal
Seal of
Institution
Annexure - I
Part A: Micro Project Proposal
1.0 Aim/Benefits of the Micro-Project:
The aim of our micro-project is to test the Movie ticket booking system (Bookmyshow.com)
2.0 Course Outcomes integrated:
The theory, practical experiences and relevant soft skills associated with this course are to be taught
and implemented, so that the student demonstrates the following industry oriented COs associated with
the above mentioned competency:
a. Apply various software testing methods.
b. Prepare test cases for different types and levels of testing.
c. Prepare test plan for an application.
d. Identify bugs to create defect report of given application.
e. Test software for performance measures using automated testing tools.
3.0 Proposed Methodology:
1. Literature survey.
2. Collect information through different sources
3. Analysis of data.
4. Compilation of collected data.
4.0 Action Plan:
Sr. Planned Planned Name of
Details of the activity
No. Start date Finish date Members
1 Formation of Group & Topic Selection All members
2 Submission of Proposed Plan All members
3 Preparation of Report All members
4 Final valuation of a working Report All members
5 Presentation of Report All members
6 Submission of Final Report All members
5.0 Resource Required:
Sr.
Name of resources/Material Specifications Qty Remarks
No.
Processor: i3
1. Computer 1
RAM: 8.00 GB
2. Microsoft Word Word - 2016 1
3. Printer Hp Laser Jet 1
www.wikipedia.com
4. Book/ website name
6.0 Name of Team Members with Roll No:
Individual
Sr. Process and Total
Roll No Name of Students Presentation
No. Product
assessment (06) (04) (10)
01 1858 Pranjal Tamuli
02 1859 Rutuja Vaidya
03 1860 Reyan Dabre
Name & Signature of Faculty: Mrs. Seema Kaimal
Annexure- II
Final Micro Project Report
Title: Testing a Railway Reservation (IRCTC) Website
Rationale: In today's software environment writing bug-free code is challenging task, which make software
testing important tool to get the quality software. Testing techniques include the process of executing a program
or application with the intent of finding software bugs and verifying that the software product is fit for use.
Students will learn the way to find bugs by applying types, levels and methods of software testing on applications
with effective test planning approach. It also covers manual testing.
2.0 Course Outcomes Integrated:
The theory, practical experiences and relevant soft skills associated with this course are to be taught
and implemented, so that the student demonstrates the following industry oriented COs associated with
the above mentioned competency:
a. Apply various software testing methods.
b. Prepare test cases for different types and levels of testing.
c. Prepare test plan for an application.
d. Identify bugs to create defect report of given application.
e. Test software for performance measures using automated testing tools.
3.0 Actual Procedure Followed.
1. Discussion about topic with guide and among group members.
2. Literature survey
3. Information collection
4. Compilation of content
5. Report presentation
4.0: Actual Resources Required:
Sr.
Name of resources/Material Specifications Qty Remarks
No.
Processor: i3
1. Computer 1
RAM: 8.00 GB
2. Microsoft Word Word -2016 1
3. Printer Hp Laser Jet 1
www.wikipedia.com
4. Book/Site name
5.0 Skill Developed/Learning outcomes of this Micro-Project
The following skills were developed:
1. Teamwork: Learned to work in a team and boost individual confidence.
2. Problem-Solving: Developed good problem-solving habits.
3. Technical Writing: Preparing the report of proposed plan and the final report.
Annexure - III
Rubrics for Assessment of Micro-Project
Title: Testing a Railway Reservation (IRCTC) Website
Institute Code: 0093 Academic year: 2024-25
Program: CO-5-I Course & Code: STE (22518)
Name of Candidate: PRANJAL TAMULI
RUTUJA VAIDYA
REYAN DABRE Roll No: 1858,1859,1860
Semester: Fifth Name of Faculty: Mrs. Seema Kaimal
Sr. Poor Average Good Excellent
Characteristic to be Assessed
No. (Marks 1-3) (Marks 4-5) (Marks 6-8) (Marks 9-10)
1. Relevance to the Course
Literature Survey/Information
2.
Collection
3. Project Proposal
Completion of the Target as per
4.
Project Proposal
5. Analysis of Data and Representation
6. Quality of Prototype/Model
7. Report Preparation
8. Presentation
9. Viva
Name & Signature of Faculty: Prof. Seema Kaimal
Annexure- IV
Micro-Project Evaluation Sheet
Title: Testing an Railway Reservation ( IRCTC ) Website
Institute Code: 0093 Academic year: 2024-25
Program: CO-5-I Course & Code: STE (22518)
Name of Candidate: Roll No: 1858,1859,1860
PRANJAL TAMULI
RUTUJA VAIDYA
REYAN DABRE
Semester: Fifth
Name of Faculty: Mrs.Seema Kaimal
Course Outcomes Achieved:
a. Apply various software testing methods.
b. Prepare test cases for different types and levels of testing.
c. Prepare test plan for an application.
d. Identify bugs to create defect report of given application.
e. Test software for performance measures using automated testing tools.
Evaluation as per Suggested Rubric for Assessment of Micro Project:
Sr. Characteristic Poor Average Marks Good Excellent Sub
No. to be assessed Marks 4-5 Marks 6-8 Marks Total
1-3 9-10
(A) Process and product assessment Out Of 6
1 Relevance to the
course
2 Literature Survey .
Information
Collection
3 Completion of
the Target as
per project
proposal
4 Analysis of
Data and
representation
5 Quality of
Prototype/Model/
Content
6 Report Preparation
(B) Individual Presentation/Viva Out of 4
7 Presentation
8 Viva
Name and designation of the Faculty Member: Mrs. Seema Kaimal
Weekly Activity Sheet
Topic: Testing a Railway Reservation (IRCTC) Website
Institute Code: 0093 Academic year: 2024-25
Program: CO-5-I Course & Code: STE (22518)
Name of Candidate: PRANJAL TAMULI
RUTUJA VAIDYA
REYAN DABRE Roll No: 1858,1859,1860
Semester: Fifth Name of Faculty: Mrs.Seema Kaimal
SR. NO WEEK ACTIVITY PERFORMED
1. 1st Week Discussion and Finalization of Topic
2. 2nd Week Literature Review
3. 3rd Week Submission of Proposed Plan
4 4th Week Information Collection
5. 5th Week Analysis of Data
6. 6th Week Compilation of content
7. 7th Week Editing and Revising the Content
8. 8th Week Report Preparation
9. 9th Week Report Preparation
10. 10th- 12th Week Presentation
Signature of Student Dated Signature of Faculty
Acknowledgement
We would like to take this opportunity to express our heartfelt gratitude to everyone
who has supported us throughout the various stages of this microproject. The journey
has been both challenging and rewarding, and it would not have been possible without
the contributions of so many dedicated individuals.
We are especially indebted to Prof. Seema Kaimal for her invaluable guidance and
insightful suggestions. Her mentorship has been instrumental in bringing this project
to fruition. Prof. Kaimal’s encouragement pushed us to think creatively, embrace new
ideas, and approach our work with confidence. Her unwavering support and
constructive feedback inspired us to strive for excellence and overcome obstacles
along the way.
I would also like to extend my sincere thanks to my parents and friends, whose
unwavering support and encouragement provided the motivation we needed to
finalize this project within a tight timeline. Their belief in our abilities helped us stay
focused and determined, even during the most stressful moments. I am truly grateful
for their understanding, patience, and love throughout this process.
Finally, I am deeply appreciative of everyone who contributed, whether through
direct assistance or moral support, to the successful completion of this endeavor.
Each of you played a vital role in making this project a reality, and I will always
cherish the collaborative spirit and shared dedication that made it all possible
1 SOFTWARE TESTING MICROPROJECT
INTRODUCTION
Software testing is the process of evaluating a software system or
application to determine whether it meets the specified requirements
and works as expected. The primary goal of software testing is to
identify defects, errors, or bugs in the software and ensure that it is
reliable, stable, and meets the user's expectations.
OBJECTIVES:
Verify that the software meets the specified requirements and
works as expected:
Validate user requirements
Ensure software functionality meets the specified requirements
Verify that the software works as expected in different environments
and scenarios
Identify defects, errors, or bugs in the software:
Detect bugs and errors early in the development cycle
Identify defects in the software functionality, performance, and
usability
Report defects and errors to the development team for fixing
Ensure the software is reliable, stable, and meets the user's
expectations:
Ensure the software is reliable and stable in different environments and
scenarios
Meet the user's expectations in terms of functionality, performance, and
usability
Ensure the software is compatible with different hardware and software
configurations
Provide feedback to the development team to improve the software
quality:
Provide detailed reports of defects and errors found during testing
Suggest improvements to the software functionality, performance, and
usability
Collaborate with the development team to ensure that defects are fixed
and improvements are implemented.
2 SOFTWARE TESTING MICROPROJECT
WHAT IS A TEST CASE?
A test case is a defined format for software testing required to check if
a particular application/software is working or not. A test case consists
of a certain set of conditions that need to be checked to test an
application or software i.e. in more simple terms when conditions are
checked it checks if the resultant output meets with the expected output
or not. A test case consists of various parameters such as ID, condition,
steps, input, expected result, result, status, and remarks.
Parameters of a Test Case:
Module Name: Subject or title that defines the functionality of the test.
Test Case Id: A unique identifier assigned to every single condition in
a test case.
Tester Name: The name of the person who would be carrying out the
test.
Test scenario: The test scenario provides a brief description to the
tester, as in providing a small overview to know about what needs to be
performed and the small features, and components of the test.
Test Case Description: The condition required to be checked for a
given software. for eg. Check if only numbers validation is working or
not for an age input box.
Test Steps: Steps to be performed for the checking of the condition.
Prerequisite: The conditions required to be fulfilled before the start of
the test process.
Test Priority: As the name suggests gives priority to the test cases that
had to be performed first, or are more important and that could be
performed later.
Test Data: The inputs to be taken while checking for the conditions.
Test Expected Result: The output which should be expected at the end
of the test.
Test parameters: Parameters assigned to a particular test case.
Actual Result: The output that is displayed at the end.
Environment Information: The environment in which the test is
being performed, such as the operating system, security information,
the software name, software version, etc.
3 SOFTWARE TESTING MICROPROJECT
Status: The status of tests such as pass, fail, NA, etc.
Comments: Remarks on the test regarding the test for the betterment of
the software.
Example:
4 SOFTWARE TESTING MICROPROJECT
TEST CASES FOR MOVIE TICKET BOOKING WEBSITE
1.BOOKMYSHOW
TESTID TEST STEP INPUT EXPECTED ACTUAL STATUS
RESULT RESULT
TC_1 Open the Select Movie details All the PASS
Bookmysho movie page threaters and
w app and "Avengers (showtimes, showtimes
select a : theatre options) displayed
movie from Endgame" should be
the homepage displayed
TC_2 Select a Select Seat selection Seat PASS
theatre and theatre page will be selection
showtime for "PVR displayed. displayed
the selected Cinemas"
movie. and
showtime
"7:30 PM"
TC_3 Select seats Click on Payment options Payment PASS
for the "Proceed page will be option
movie. to Pay" displayed displayed
(Credit/Debit
Card, UPI, etc.).
5 SOFTWARE TESTING MICROPROJECT
1. Test Scenario ID:
This column contains the IDs of various test scenarios that group
related test cases together. For example, Ts-1 and Ts-2 are related to
checking URLs and sign-in processes.
2. Test Scenario:
Each test scenario describes a broader test activity.
Ts-1 is checking the URL.
Ts-2 is checking the Sign In functionality.
Ts-3 is related to checking the login with valid data.
3. Test Case ID:
This column assigns unique identifiers to individual test cases.
Tc-1 through Tc-10 are individual test cases under the broader
scenarios.
Each test case checks a specific functionality within the scenario (e.g.,
entering valid/invalid mobile numbers, checking OTP input).
4. Test Steps:
This column contains detailed steps that testers must follow during the
test.
For example, in Tc-2, the tester is instructed to "Click Sign in."
In Tc-5, the step is to "Enter invalid mobile number click login."
5. Input:
This column shows the input values to be used during the test.
For example, in Tc-3, the input is a mobile number (Mobile Number:
**********).
In Tc-5, the input is an invalid mobile number (121.644.454).
6. Expected Result:
This column shows the expected behavior if the system works
correctly.
In Tc-5, the expected result is that the system should display a message
like "Please enter the valid mobile number."
7. Actual Result:
This column is used to record what actually happens when the test is
run.
In Tc-5, the actual result is that the invalid mobile number is accepted,
which is a failure as the expected result was an error message.
6 SOFTWARE TESTING MICROPROJECT
8. Result:
This column indicates whether the test case passed or failed.
A "Pass" means the actual result matched the expected result.
A "Fail" means the actual result did not meet expectations (e.g., in Tc-
6, the test failed because an invalid email ID was accepted).
Summary:
This table is used to evaluate whether different aspects of the login
system are functioning as expected. The test cases include steps like
entering valid and invalid mobile numbers, email addresses, and OTPs.
Any mismatch between the expected and actual results is marked as a
failure, indicating areas that need to be fixed.
2nd test case:
1. TESTID:
o Identifies the test case.
o TC_1, TC_2, and TC_3 are the unique IDs assigned to each
test case.
2. TEST STEP:
o Describes the specific action that a tester needs to perform
for each test.
For TC_1: The step is to open the BookMyShow app
and select a movie from the homepage.
For TC_2: The step is to select a theatre and showtime
for the chosen movie.
For TC_3: The step is to select seats and click on
"Proceed to Pay."
3. INPUT:
o The actual input data used during the testing.
For TC_1: The tester selects the movie "Avengers:
Endgame."
For TC_2: The tester selects "PVR Cinemas" and a
showtime of "7:30 PM."
For TC_3: No specific seats are mentioned, but the
user clicks "Proceed to Pay."
4. EXPECTED RESULT:
7 SOFTWARE TESTING MICROPROJECT
o Describes what the system should display or perform after
the test step is completed.
For TC_1: The movie details page with showtimes
and theatre options should be displayed.
For TC_2: The seat selection page should appear.
For TC_3: The payment options page should appear,
showing methods like Credit/Debit Card, UPI, etc.
5. ACTUAL RESULT:
o Describes what actually happened during the testing
process.
In all three test cases (TC_1, TC_2, and TC_3), the
expected behavior occurred as described.
For TC_1, all the theatres and showtimes were
displayed.
6. STATUS:
o Indicates whether the test passed or failed.
All test cases in this table (TC_1, TC_2, and TC_3)
have a status of "PASS," meaning the actual results
matched the expected results.
Summary:
This table documents the test of a movie booking flow in the
BookMyShow app, from selecting a movie (Avengers: Endgame),
choosing a theatre and showtime (PVR Cinemas, 7:30 PM), selecting
seats, and proceeding to the payment page. All tests passed
successfully, confirming that the system behaved as expected during
this sequence of actions.
8 SOFTWARE TESTING MICROPROJECT
DEFECT REPORT:
Report_ID: DEF-002
Project: Movie Ticket Booking Website Testing
Product: BookMyShow
Release Version: N/A
Module: Payment Gateway & User Interface
Summary: Incorrect validation for invalid mobile number during login
on BookMyShow.
Description: During the login process, the system allows users to input
an invalid mobile number and proceed without any error message. The
system should validate the mobile number format and display an
appropriate message when an invalid number is entered. This issue was
observed on multiple devices and browsers.
Reported By: Pranjal
Assigned To: Rutuja
Defect Severity: Major
Defect Priority: High
Status: Open
Steps to Reproduce the Defect:
Launch the BookMyShow app.
Navigate to the login page.
Enter an invalid mobile number (e.g., 121.644.454).
Attempt to log in.
Observe that the invalid mobile number is accepted without any error
message.
Expected Result: The system should display an error message like
"Please enter a valid mobile number" when an invalid number is
entered.
Actual Result: The system accepts the invalid mobile number and
allows users to proceed.
9 SOFTWARE TESTING MICROPROJECT
CONCLUSION
In conclusion, software testing is an essential process to ensure that
applications function as expected and meet user requirements. Through
this project, we identified critical defects, such as validation errors in
the BookMyShow login system, and demonstrated the importance of
detecting and reporting such issues early in the development cycle.
These defects can significantly impact user experience if not resolved
promptly. By thoroughly testing and reporting errors, we contribute to
improving the software’s reliability, performance, and usability,
ensuring a more stable and user-friendly product.
10 SOFTWARE TESTING MICROPROJECT
REFERNCES
Test Case Description and Steps: The document provides detailed
examples of test cases, including steps for logging in and booking
tickets on a platform like BookMyShow. The defect report follows
similar steps for the login test case (invalid mobile number scenario).
Expected vs. Actual Result: The document outlines how expected
results are compared with actual outcomes, which is used in the defect
report to highlight the issue of accepting invalid mobile numbers
without appropriate error handling(stemicro).
Defect Reporting Structure: The document also includes a defect
report format, which has been adapted for the current issue (invalid
mobile number validation in the BookMyShow system)(stemicro).
Additional References:
www.GeeksForGeeks.com
www.wikipedia.com
