QA Manual Testing Assessment

QuickBite - Online Food Ordering Application

Duration: 1 hour

Application: QuickBite Food Ordering Web App (open in browser)

Goal: Find and document as many bugs/issues as possible

Tools: Use the provided text editor or pen/paper for your bug reports

Background

QuickBite is a food ordering web application where users can browse a menu, add items to their cart, apply promo codes, and place orders through a checkout form. The application has several bugs and issues that need to be identified.

Your Task

Explore the application thoroughly - Test all features including menu browsing, search, category filtering, cart operations, promo codes, and the checkout process.
Find bugs and issues - Look for functional bugs, validation issues, UI inconsistencies, calculation errors, and usability problems.
Document each bug - Write a clear bug report for every issue you find using the template below.

Bug Report Template

Bug Title: [Short, descriptive title]
Severity: [Critical / High / Medium / Low]
Steps to Reproduce:
  1. [First step]
  2. [Second step]
  3. [Continue as needed]
Expected Result: [What should happen]
Actual Result: [What actually happens]

Areas to Test

Promotional banner and promo codes
Menu items and category filtering
Search functionality
Adding/removing items from cart
Cart calculations (subtotal, tax, discounts, total)
Checkout form validation (all fields)
Payment method selection
Order placement and confirmation

Severity Guide

Critical: App crashes, data loss, security vulnerability, payment errors
High: Major feature not working, incorrect calculations, misleading information
Medium: Feature works but incorrectly, wrong messages, poor validation
Low: Minor UI issues, cosmetic problems, minor usability concerns

        Tip: Don't just test the "happy path". Try unexpected inputs, edge cases, and unusual user flows.
        Quality of your bug reports matters as much as the quantity of bugs found.
    