Scribd
Upload
61 views7 pages

Swiggy

Uploaded by

co2022.akshay.parab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
61 views7 pages

Swiggy

Uploaded by

co2022.akshay.parab
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

*Test Plan for Swiggy App*

1. Introduction
The Swiggy App is a food delivery platform that allows users to browse restaurants, place
orders, and track deliveries in real-time. It supports various payment options and offers
personalized deals to enhance user experience.

1.1 Scope
*1.1.1 In Scope*
- User Registration and Authentication
- Restaurant Search and Browsing
- Food Ordering and Payment Processing
- Delivery Tracking and Notifications
- Customer Support Chat

*1.1.2 Out of Scope*


Real-Time GPS Tracking Accuracy: The precision of GPS tracking beyond standard
functionality.
Discount and Coupon Analytics: Detailed testing of how discounts affect Swiggy's financial
metrics.

1.2 Quality Objectives


The test objectives of swiigy application is to- Ensure accurate order placement and tracking.
- Validate secure and smooth payment processing.
- Verify seamless browsing and restaurant search functionalities.

1.3 Roles and Responsibilities


- *Test Manager*: Coordinate test planning and execution.
- *Testers*: Execute test cases, identify, and report defects.
- *Developers*: Fix reported defects and provide technical support.

---

2. Test Methodology
2.1 Overview
Unit tests focus on individual modules like user authentication, restaurant search, and order
management to ensure functionality and reliability. Integration testing validates the interaction
between modules, such as order placement with payment processing and order tracking with
delivery updates. Additionally, end-to-end testing ensures the app flows seamlessly, from user
login to order completion and delivery confirmation, across all supported devices and platforms.
2.2 Test Levels
Unit Testing: Validate each module in isolation.
Integration Testing : individual modules are combined together
System testing : conducted on complete, integrated software
Api testing :

2.3 Bug Triage


Critical defects will be prioritized and resolved before further testing to ensure minimal disruption
to the testing process. Medium and low-priority issues will be logged and addressed in
subsequent development cycles based on their impact on the overall functionality and user
experience.

2.4 Suspension Criteria and Resumption Requirements


If a team member reports that there are 30% test cases failed then test case will continue
execution until all test cases failed are been fixed

2.5 Test Completeness


->Testing is considered complete upon executing all planned test cases successfully.
->the run rate should be 100% unless a clear reason is given
-->pass rate should be 80% which is mandatory

2.6 project task & estimation & schedule

---
3. Test Deliverables

4. Resources and Environment Needs

##### 4.1 Testing Tools

4.2 Test Environment


- *Server Requirements*:
- A test environment simulating Swiggy’s backend services, including order management,
delivery logistics, restaurant inventory, and payment gateway integration.

- *Device Matrix*:
- A mix of Android and iOS devices with varying screen sizes to ensure compatibility with all
users.

- *Network Configurations*:
- Testing under different network conditions (e.g., 2G, 3G, 4G, 5G, Wi-Fi) to evaluate app
performance during peak usage and under variable connectivity.

- *Test Data*:
- Simulated restaurant data (menus, prices, availability) and user profiles (address, order
history).
- Dummy payment and discount data for testing order and checkout functionality.
- Fake delivery addresses and delivery tracking data for testing the delivery process.

#### 5. Terms/Acronyms
*Test Summary Report for Swiggy App*

### 1. Purpose of the Document


This document provides a summary of the testing efforts for the Swiggy App to validate its
functionality, reliability, and readiness for deployment.

### 2. Application Overview


The Swiggy App enables users to browse restaurant menus, place food orders, and track
deliveries. It supports multiple payment options and real-time notifications.

### 3. Testing Scope


#### 3.1 In Scope
- User Authentication
- Restaurant Browsing and Search
- Order Placement and Payment
- Delivery Tracking and Notifications
- Customer Support Chat

#### 3.2 Out of Scope


- Load Testing during peak hours
- Compatibility Testing across all devices

---

### 4. Metrics
### 5. Types of Testing Performed
- Unit Testing
- Functional Testing
- Usability Testing

### 6. Test Environment and Tools


- Test Environment: Simulated restaurant servers and delivery tracking
- Tools: Selenium, Postman, JIRA

---

### 7. Lessons Learned


- Early bug identification improved delivery tracking accuracy.
- Payment gateway integration required additional testing.

### 8. Recommendations
- Conduct performance testing during peak ordering times.
- Enhance compatibility testing for legacy devices.

### 9. Best Practices


- Automate repetitive test cases for order workflows.
- Encrypt sensitive user data during testing phases.
### 10. Exit Criteria
Testing is deemed complete when all high-priority test cases pass and critical defects are
resolved.

### 11. Conclusion


The Swiggy App meets its functional requirements and is ready for deployment, with minor
issues logged for resolution in future updates.

### 12. Definitions, Acronyms, Abbreviations


- *API*: Application Programming Interface
- *JIRA*: Bug Tracking Tool

You might also like