Scribd
Upload
42 views3 pages

STE Practical8

Uploaded by

dnyanda0407
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
42 views3 pages

STE Practical8

Uploaded by

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

Test Plan for Swiggy Application

1. Introduction

The Swiggy application is a mobile platform designed for food delivery services. Users can order food
from a variety of restaurants and have it delivered to their doorstep. This test plan outlines the
approach and strategy to validate the application's core functionalities to ensure they meet user
expectations and quality standards.

2. Objective

The objective of this test plan is to verify that key functionalities of the Swiggy application work as
intended, ensuring a smooth and efficient user experience. The focus will be on user authentication,
search capabilities, cart functionality, checkout processes, payment handling, and location
permission requests.

3. Scope

The scope of this testing includes:

 Functional testing of the application’s core features.


 Validation of the user interface and navigation flow.
 Testing for error handling and messaging.
 Compatibility testing across various devices and operating systems.
 Security testing related to user data handling and payment processing.

4. Test Environment

 Devices: Android and iOS smartphones

 Operating Systems: Latest versions of Android and iOS

 Network Conditions: Wi-Fi and mobile data (3G, 4G)

 Application Version: The latest build of the Swiggy application

 Testing Tools: Manual testing tools, Bug tracking tool (e.g., JIRA), Test management tool (e.g.,
TestRail)
5. Test Cases

Test Case Objective Preconditio Test Steps Expected Actual Result Status
ID n Result
TC-001 Verify login User has an 1. Launch User should User is Pass
with valid account the app logged in and logged in and
credentials 2. Click navigated to navigated to
"Login" the home the home
3. Enter page page
valid
credentials
4. Click
"Submit"
TC-002 Verify User is 1. Use the Relevant Relevant fail
search logged in search bar restaurant or restaurant or
functionality 2. Enter a food item food item
restaurant results results are
or food item should be not
name displayed displayed
3. Press
"Search"

TC-003 Verify User is 1. Select a Item should Item is Pass


adding item logged in dish from successfully successfully
to cart and on the added to the added to the
restaurant restaurant cart cart
page menu
2. Click
"Add to
Cart"
TC-004 Verify Items are in 1. Go to cart Order should Order is Pass
checkout the cart 2. Click successfully successfully
process "Checkout" placed, and placed, and
3. Enter order order
delivery confirmation confirmation
address screen screen is
4. Choose should be displayed
payment displayed
method
5. Click
"Place
Order"
TC-005 Verify Items are in 1. Go to Payment an error Fail
handling of cart, invalid checkout should fail, message is
payment payment 2. Select a and an error not
failure details payment message displayed
available method should be
3. Enter displayed
incorrect
payment
details
4. Click
"Pay"
TC-006 Verify User is 1. Launch App prompts App prompts Pass
location launching the app the user to the user to
permission the app for 2. Check for grant location grant location
request the first time location access access
access
permission
request

6. Test Execution

 Execution Strategy: Tests will be executed manually based on the defined test scenarios.

 Execution Timeline: The testing phase will occur over two weeks, with results reviewed daily.

 Test Execution Reporting: A daily status report will be generated to track progress,
highlighting any defects identified during testing.

7. Defect Management

 Defect Tracking Tool: All defects will be logged using JIRA for tracking and management
purposes.

 Defect Life Cycle: Each defect will follow the stages: New, Assigned, In Progress, Resolved,
and Closed.

 Priority Levels: Defects will be categorized based on their severity and impact on user
experience (Critical, Major, Minor).

8. Conclusion

This test plan aims to ensure that the Swiggy application meets functional requirements and provides
a high-quality user experience. All identified defects will be addressed and resolved before the final
release, enhancing the overall application quality and performance. Successful execution of this test
plan will contribute to delivering a reliable food delivery service for users.

You might also like