DEPARTMENT OF COMPUTER ENGINEERING,

PCET’S PIMPRI CHINCHWAD COLLEGE OF ENGINEERING

Sector No. 26, Pradhikaran, Nigdi, Pune – 411044

FA2 REPORT
on

“Comprehensive Testing Strategy for Uber-like Software Application”

By

PRN: Name:
121B1B222 Satyam Mirgane
122B2B223 Tarun Rathod
122B2B224 Sarthak Shelar

Under the Guidance of

Geetanjali Sharma

PCET’S PIMPRI CHINCHWAD COLLEGE OF ENGINEERING

Sector No. 26, Pradhikaran, Nigdi, Pune – 411044
 1. Introduction
Our team designed a comprehensive testing strategy for an Uber-like ride-hailing application, covering
all critical modules, including user registration, ride booking, payment processing, real-time
communication, and the admin panel. The primary objective of the testing strategy is to ensure the
reliability, security, scalability, and usability of the application. Each phase of the strategy is
meticulously designed to identify bugs, performance bottlenecks, and security vulnerabilities to deliver a
seamless user experience.

This document presents a detailed breakdown of the testing types, test plans, and specific test cases used.
We employed various testing methodologies, including functional testing, integration testing,
performance testing, security testing, and user acceptance testing (UAT), to ensure the application
meets both technical and business requirements.

2. Scope of Testing
The testing strategy focuses on validating the following essential features and modules:

1. User Registration & Authentication:

○ Users should be able to register, log in, and reset their passwords securely.
○ Social media or third-party logins should function correctly (e.g., Google/Facebook
authentication).
○ Email and phone OTP verification processes must be validated.

2. Ride Booking System:

○ Users can select pickup and drop-off locations on an interactive map.
○ Fare estimation should account for distance, surge pricing, and promotional discounts.
○ Users should view driver details (name, vehicle, ETA) in real-time.

3. Payment Processing:
○ Support for multiple payment options: credit cards, UPI, wallets, and cash.
○ Ensure transaction logs are accurate, with invoices generated correctly.
○ Payment refund and cancellation flows need validation.

4. In-App Communication:
○ Users and drivers should engage in real-time chat or voice calls.
○ Notification systems (e.g., SMS, push notifications) must alert users about ride status.

5. Rating & Review System:

○ Users should be able to rate and review drivers, and vice versa.
○ Ratings should be aggregated correctly, and suspicious reviews should be flagged.
 6. Admin Panel:
○ Admins can manage drivers, users, complaints, and suspend or ban accounts.
○ Reporting tools should provide detailed insights into rides, revenue, and user activity.

3. Testing Types and Methodology

3.1 Functional Testing

● Objective: Validate that individual features work according to business requirements.

● Scope: Includes both positive and negative test cases (e.g., valid login vs. invalid credentials).
● Outcome: Ensures core functionality works across various conditions and edge cases.

3.2 Integration Testing

● Objective: Ensure that all modules interact and exchange data correctly.
● Scope: Focuses on workflows between ride booking, payment, and communication systems.
● Outcome: Verifies smooth data exchange between multiple components.

3.3 Performance Testing

● Objective: Assess the speed, scalability, and stability of the system under load.
● Scope: Tests with increasing loads and concurrent users to simulate peak conditions.
● Outcome: Identifies performance bottlenecks and ensures scalability.

3.4 Security Testing

● Objective: Identify vulnerabilities to prevent data breaches and fraud.

● Scope: Focuses on authentication, payment encryption, and SQL injection protection.
● Outcome: Ensures that the app complies with security standards and protects sensitive data.

3.5 User Acceptance Testing (UAT)

● Objective: Confirm that the system meets user expectations and business goals.
● Scope: Involves end-users performing real-world tasks, such as booking a ride and making
payments.
● Outcome: Validates that the final product aligns with business needs and delivers value.

4. Detailed Test Plan

Our test plan includes test objectives, scope, tools, and responsibilities. We have broken it down into
functional, integration, performance, and security testing. Below, detailed test case tables provide a
clear picture of test scenarios, inputs, expected results, and status tracking.

5. Detailed Testing Tables

 5.1 Functional and Integration Testing Table

This table ensures that every feature works as expected both independently and when integrated with other
components.

Test Case Module Test Description Input/Action Expected Result Status

ID

TC-01 User Validate Enter valid name, User is registered Passed

Registration successful email, phone, and and redirected to
registration password dashboard

TC-02 User Validate OTP Enter valid OTP sent and Passed
Registration verification for phone/email, validated
phone/email request OTP successfully

TC-05 Ride Booking Test surge pricing Request a ride Fare includes surge Passed
during high during peak hours multiplier
demand

TC-06 Ride Booking Test booking Cancel ride after Refund processed Passed
cancellation flow booking based on
cancellation policy

TC-09 Communication Validate in-app User calls driver via Voice call Passed
voice call feature in-app interface connected without
issues

TC-12 Admin Panel Test driver Admin suspends Driver status Passed
suspension driver account updated to
feature "Suspended"

5.2 Performance Testing Table

Performance testing ensures the app behaves correctly under different loads and stress conditions.

Test Module Test Description Load Scenario Expected Result Tool

Case Used
ID

PT-01 Ride Test with 10,000 Simulate 10,000 App handles load JMeter
Booking concurrent users ride booking with <2-second
System requests response time
 PT-02 Payment Test with 5,000 Simulate 5,000 All transactions JMeter
Processing simultaneous payment requests complete within 3
transactions seconds

PT-03 In-App Assess messaging Simulate 1,000 Message delivery in Apache

Messaging delay under peak concurrent chat real-time with no Bench
load sessions lag

5.3 Security Testing Table

The security testing phase identifies vulnerabilities and ensures user data is protected.

Test Module Test Description Test Type Expected Tool Used

Case Result
ID

ST-01 User Test SQL injection Input ' OR 1=1 Login blocked OWASP
Authentication vulnerability -- as username with error ZAP
message

ST-02 Payment Test for encrypted Intercept Credit card Burp

Gateway credit card payment with details Suite
transactions proxy tool encrypted

ST-03 Data Storage Check for Scan storage No sensitive Nessus

unencrypted using security data in
sensitive data scanner plaintext

ST-04 Communication Test for end-to-end Intercept chat All messages Wireshark
Module chat encryption using proxy encrypted

6. User Acceptance Testing (UAT)

During UAT, a pilot group of users and stakeholders tested the application by performing real-world
tasks, such as booking rides, chatting with drivers, and completing payments. Feedback was collected, and
any identified issues were resolved before launch. The testing focused on:

● Ride booking flow: Verifying smooth ride searches and booking.

● Driver interaction: Testing real-time messaging and ETA updates.
● Payment and refund flows: Ensuring secure and correct transactions.
● Admin reports: Validating that admins can generate reports efficiently.

7. Regression Testing
Regression testing is critical after every bug fix or feature update. Automated test cases will cover:

● Login, ride booking, payment, and chat modules.

● Ensures that previously working features remain unaffected by new changes.
● Tools used: Selenium for automation and JMeter for load testing.

8. Conclusion
Our detailed testing strategy covers all aspects of the Uber-like ride-hailing application, including
functionality, integration, performance, security, and usability. We ensured that the application meets
high-quality standards and operates smoothly under various conditions. Regression testing and
continuous monitoring will be incorporated to maintain system stability.

This comprehensive approach guarantees that the application is secure, user-friendly, and scalable,
ensuring a superior experience for both drivers and riders.