Friday, July 4, 2025

Case Study: Testing a Food Delivery App (Real Project Tasks)

πŸ“¦ Case Study: Testing a Food Delivery App (Real Project Tasks)

In this case study, I’ll walk you through how I tested a real-world food delivery application, covering the different types of testing I performed and the actual modules I worked on.

πŸ“± Application Overview

  • Platform: Web and Mobile App (iOS & Android)
  • Users: Super Admin, Restaurant Admin, Customer, Delivery Boy
  • Tech Stack: React, Node.js, MongoDB, Firebase

πŸ§ͺ Testing Types Performed

  • Functional Testing – Verified core features like order placement, payment, and delivery flow.
  • UI Testing – Checked responsiveness, alignment, and element visibility across devices.
  • Regression Testing – After each deployment or feature enhancement.
  • Cross-Browser Testing – Chrome, Firefox, Safari compatibility for web interface.
  • API Testing – Used Postman to validate RESTful endpoints for user login, orders, and menu updates.

πŸ§‘‍πŸ’» Modules Tested

  • πŸ” User Registration & Login (OTP & Email-based)
  • πŸ” Restaurant Menu Management (CRUD operations)
  • πŸ›’ Cart & Checkout Flow (Add, remove items, promo codes)
  • πŸ’³ Payment Integration (Razorpay/Stripe sandbox testing)
  • 🚴 Order Assignment to Delivery Boys
  • πŸ“ Real-Time Order Tracking (Google Maps)
  • πŸ“Š Admin Dashboard Analytics & Reports

πŸ“ Sample Test Case Table

Test Case Expected Result Status
The user places an order with a valid payment The order should be accepted and visible in the order history Pass
The delivery boy accepts the order Status changes to "Out for delivery" Pass
Invalid promo code applied Display appropriate error message Pass

🐞 Bugs Found

  • Promo code applied multiple times in the cart
  • The order tracking map is not loading on iOS
  • Menu item image upload fails on slow network
  • Delivery boy app crashes on auto logout

πŸ”š Conclusion

This project helped me gain practical experience in end-to-end QA for a multi-user food delivery ecosystem. It involved API testing, real-time validations, UI cross-checks, and regression cycles. A strong reminder that good testing means thinking like both the customer and the developer.

πŸ‘‹ Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

πŸ“¬ Contact Me | LinkedIn | GitHub

πŸ“Œ Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

No comments:

Post a Comment