What Are the Test Cases for Flipkart Website?
Rimpal Mistry Testscenario
26/02/2025
QA teams that implement test cases for the Flipkart website validate 8 functional areas: login, search, product pages, cart, wishlist, checkout, payment, and order management. Flipkart test cases cover the complete user journey from OTP-based authentication to payment confirmation. QA testing teams use these test cases to verify that every interaction on the platform produces the expected result across Android, iOS, and web.
This guide provides test cases, test scenarios, and testing methodology for 8 areas of the Flipkart application. Each section includes a test case table with test case ID, scenario, steps, and expected outcome.
What Are the Test Cases for Flipkart Login Page?
The test cases for the Flipkart login page validate OTP-based mobile authentication, session handling, and account security. Flipkart uses mobile number and OTP verification for login. Flipkart does not use traditional username and password authentication. OTP delivery and verification across SMS and WhatsApp channels form the core of login testing.
How Does Flipkart OTP-Based Login Work for Testing?
Flipkart OTP-based login works through a 3-step process: mobile number entry, OTP delivery, and OTP verification.
QA teams test each step independently. The mobile number field accepts 10-digit Indian numbers. The OTP field accepts 6-digit numeric codes. OTP delivery occurs through SMS or WhatsApp. OTP expiration occurs after 5 minutes.
What Are the Negative Test Cases for Flipkart Login?
Negative test cases for Flipkart login verify that invalid inputs produce appropriate error messages.
Negative scenarios include invalid mobile numbers, expired OTPs, incorrect OTPs, and exceeding the maximum OTP request limit. Each negative test case confirms that Flipkart blocks the login attempt and displays a specific error message.
| Test Case ID | Scenario | Steps | Expected Outcome |
|---|---|---|---|
| FL-001 | Login with valid mobile number and OTP | 1. Enter valid 10-digit mobile number 2. Click “Request OTP” 3. Enter the received 6-digit OTP |
OTP is verified. User is redirected to the homepage. |
| FL-002 | Login with invalid mobile number | 1. Enter a number with fewer than 10 digits 2. Click “Request OTP” |
Error: “Please enter a valid mobile number.” |
| FL-003 | Login with expired OTP | 1. Enter valid mobile number 2. Wait 5 minutes after OTP delivery 3. Enter the expired OTP |
Error: “OTP has expired. Please request a new one.” |
| FL-004 | Login with incorrect OTP | 1. Enter valid mobile number 2. Enter an incorrect 6-digit OTP |
Error: “Incorrect OTP. Please try again.” |
| FL-005 | Exceed maximum OTP requests | 1. Request OTP 5 times within 10 minutes 2. Attempt a 6th request |
Error: “Too many OTP requests. Try again later.” |
| FL-006 | Login via existing account with email | 1. Click “Login with Email” 2. Enter registered email and password |
User is logged in and redirected to the homepage. |
| FL-007 | Password reset for email-based account | 1. Click “Forgot Password” 2. Enter registered email 3. Follow the reset link 4. Set a new password |
Password reset is successful. User logs in with the new password. |
| FL-008 | Login session persistence after app close | 1. Log in successfully 2. Close the Flipkart app 3. Reopen the app |
User remains logged in without re-authentication. |
Login test cases cover authentication. Search test cases cover how users find products after logging in.
What Are the Test Cases for Flipkart Product Search and Filters?
The test cases for Flipkart product search and filters validate keyword matching, auto-suggestions, sorting accuracy, and multi-filter combinations. Flipkart search processes millions of product listings across multiple categories. Search test cases verify that the system returns relevant results for exact matches, partial matches, and misspelled inputs.
What Are the Search Functionality Test Cases for Flipkart?
Search functionality test cases for Flipkart verify that keyword input produces relevant product results within 2 seconds.
QA teams test 5 search scenarios: exact product name, partial keyword, misspelled keyword, brand name, and empty search. Each scenario validates result relevance, response time, and auto-suggestion accuracy.
| Test Case ID | Scenario | Steps | Expected Outcome |
|---|---|---|---|
| FS-001 | Search with exact product name | 1. Enter “iPhone 16 Pro Max” in the search bar 2. Click the search icon |
Search results display iPhone 16 Pro Max listings. |
| FS-002 | Search with misspelled keyword | 1. Enter “samsng galaxy” in the search bar 2. Click the search icon |
Fuzzy search returns Samsung Galaxy product listings. |
| FS-003 | Verify auto-suggestions | 1. Type “Nik” in the search bar 2. Observe the dropdown suggestions |
Auto-suggestions display “Nike shoes,” “Nikon camera,” and related terms. |
| FS-004 | Search with no matching results | 1. Enter “xyzabc123” in the search bar 2. Click the search icon |
Message: “Sorry, no results found!” |
| FS-005 | Search result pagination | 1. Search for a broad term like “shoes” 2. Scroll to the bottom of results 3. Click “Next Page” |
Next page loads with additional product listings. |
| FS-006 | Search by product category | 1. Navigate to “Electronics” category 2. Browse subcategories |
Products display under the selected category hierarchy. |
What Are the Filter and Sorting Test Cases for Flipkart?
Filter and sorting test cases for Flipkart verify that users narrow results by price, brand, rating, discount, and availability.
| Test Case ID | Scenario | Steps | Expected Outcome |
|---|---|---|---|
| FF-001 | Apply price range filter | 1. Search for “headphones” 2. Set price range ₹500 to ₹2,000 |
All displayed products fall within ₹500 to ₹2,000. |
| FF-002 | Apply brand filter | 1. Search for “running shoes” 2. Select “Nike” under Brand filter |
Only Nike running shoes appear in results. |
| FF-003 | Apply multiple filters | 1. Search for “laptop” 2. Apply Brand: “HP,” RAM: “8 GB,” Price: “₹40,000-₹60,000” |
Results match all 3 filter criteria simultaneously. |
| FF-004 | Sort by price low to high | 1. Search for “smartwatch” 2. Select “Price: Low to High” |
Products display in ascending price order. |
| FF-005 | Clear all applied filters | 1. Apply 2 or more filters 2. Click “Clear All” |
All filters are removed. Original search results are restored. |
Search results lead users to individual product pages. Product page test cases verify what users see after clicking a search result.
What Are the Test Cases for Flipkart Product Page?
The test cases for the Flipkart product page validate product attributes, image display, pricing accuracy, stock status, and delivery estimation. Each product page on Flipkart displays the title, description, images, specifications, reviews, and seller details. Product page test cases confirm that every element renders correctly and updates dynamically based on attribute selection.
How Do QA Teams Test Product Attributes on Flipkart?
QA teams test product attributes on Flipkart by selecting each variant (size, color, storage) and verifying that the price, images, and availability update accordingly.
Attribute selection triggers a dynamic update on the page. A color change updates the product image. A storage change updates the price. QA teams verify that each combination reflects the correct data from the backend.
What Are the Test Cases for Flipkart Product Page Elements?
Test cases for Flipkart product page elements cover attribute selection, stock status, image zoom, delivery estimation, seller details, and specifications display.
| Test Case ID | Scenario | Steps | Expected Outcome |
|---|---|---|---|
| FP-001 | Product attribute selection | 1. Open a product with multiple variants 2. Select a different color or size |
Price, image, and availability update for the selected variant. |
| FP-002 | Out-of-stock product handling | 1. Navigate to a product marked “Out of Stock” 2. Attempt to add it to cart |
“Add to Cart” button is disabled. “Notify Me” option is displayed. |
| FP-003 | Product image zoom | 1. Open a product page 2. Hover over the product image |
Zoomed view of the image is displayed. |
| FP-004 | Delivery estimation by pincode | 1. Enter a valid 6-digit pincode 2. Check delivery date |
Estimated delivery date is displayed for the entered pincode. |
| FP-005 | Seller details and ratings | 1. Scroll to the seller section on a product page | Seller name, rating, and return policy are displayed. |
| FP-006 | Product specifications table | 1. Scroll to “Specifications” on a product page | Complete specifications are displayed in a structured table. |
Users who confirm product details add items to the cart. Cart and wishlist test cases validate what happens after the “Add to Cart” click.
What Are the Test Cases for Flipkart Add to Cart and Wishlist?
The test cases for Flipkart add to cart and wishlist validate item addition, quantity updates, price recalculation, cart persistence, and wishlist-to-cart transfer. Cart functionality on Flipkart includes SuperCoin redemption and Flipkart Plus membership benefits. Cart test cases verify that pricing, discounts, and loyalty rewards calculate correctly across all product combinations.
What Happens When a User Adds Duplicate Products to Flipkart Cart?
Flipkart increments the item quantity when a user adds a duplicate product to the cart. The system does not create a separate line item for the same product variant.
How Does Flipkart Handle Cart Persistence Across Sessions?
Flipkart persists cart items across sessions for logged-in users. Cart items remain saved when the user closes the app or browser. Cart data syncs across devices when the user logs in with the same account.
| Test Case ID | Scenario | Steps | Expected Outcome |
|---|---|---|---|
| FC-001 | Add a product to cart | 1. Open a product page 2. Click “Add to Cart” |
Product is added. Cart icon shows updated item count. |
| FC-002 | Add duplicate product to cart | 1. Add a product to cart 2. Add the same product again |
Item quantity increments to 2. No duplicate entry is created. |
| FC-003 | Update product quantity in cart | 1. Open the cart 2. Change quantity from 1 to 3 |
Cart total recalculates based on the new quantity. |
| FC-004 | Remove a product from cart | 1. Open the cart 2. Click “Remove” on a product |
Product is removed. Cart total updates accordingly. |
| FC-005 | Apply coupon code in cart | 1. Add products to cart 2. Enter a valid coupon code 3. Click “Apply” |
Coupon discount is applied. Updated total is displayed. |
| FC-006 | Cart persistence after logout | 1. Add items to cart while logged in 2. Log out 3. Log back in |
Cart retains all previously added items. |
| FC-007 | Add product to wishlist | 1. Open a product page 2. Click the heart icon |
Product is added to the wishlist successfully. |
| FC-008 | Move product from wishlist to cart | 1. Open the wishlist 2. Click “Move to Cart” on a product |
Product moves from wishlist to cart. Wishlist entry is removed. |
| FC-009 | Apply SuperCoin discount | 1. Add eligible products to cart 2. Select “Use SuperCoins” during checkout |
SuperCoin discount is applied to the cart total. |
Cart testing ends where checkout begins. Checkout test cases pick up from the “Place Order” button and validate address, delivery, and order confirmation.
What Are the Test Cases for Flipkart Checkout Process?
The test cases for the Flipkart checkout process validate address selection, order summary accuracy, delivery option selection, and order placement confirmation. Checkout on Flipkart follows a 4-step flow: cart review, address selection, payment method selection, and order confirmation. Checkout test cases verify that each step processes correctly without data loss.
How Does Address Selection Work During Flipkart Checkout?
Address selection during Flipkart checkout allows users to choose from saved addresses or add a new delivery address. Each address requires a name, phone number, pincode, and full address.
What Are the Order Confirmation Test Cases for Flipkart?
Order confirmation test cases for Flipkart verify that the order ID is generated, the confirmation email is sent, and the order appears in the “My Orders” section.
| Test Case ID | Scenario | Steps | Expected Outcome |
|---|---|---|---|
| CO-001 | Proceed to checkout from cart | 1. Add products to cart 2. Click “Place Order” |
User is redirected to the address selection step. |
| CO-002 | Add a new delivery address | 1. Click “Add a New Address” 2. Enter name, phone, pincode, address 3. Save the address |
New address is saved and selectable for delivery. |
| CO-003 | Select delivery option | 1. Choose between Standard and Express delivery | Delivery date and cost update based on the selected option. |
| CO-004 | Place an order successfully | 1. Complete address selection 2. Select payment method 3. Click “Confirm Order” |
Order is placed. Order ID and confirmation message are displayed. |
| CO-005 | Order confirmation email | 1. Place an order 2. Check the registered email |
Confirmation email with order ID and summary is received. |
| CO-006 | Cancel an order | 1. Go to “My Orders” 2. Click “Cancel” on a recent order |
Order is cancelled. Cancellation email is sent. |
| CO-007 | Track an order | 1. Go to “My Orders” 2. Click “Track” on an active order |
Order tracking displays the current shipment status. |
| CO-008 | Request return or replacement | 1. Go to “My Orders” 2. Select a delivered order 3. Click “Return” or “Replace” |
Return or replacement request is submitted. Confirmation is displayed. |
Order placement triggers payment processing. Payment gateway test cases validate each transaction method Flipkart supports.
What Are the Payment Gateway Test Cases for Flipkart?
The payment gateway test cases for Flipkart validate 6 payment methods: UPI (PhonePe), credit card, debit card, net banking, Flipkart Pay Later, and cash on delivery. Payment testing on Flipkart verifies transaction success, failure handling, refund processing, and price accuracy including GST and shipping charges. Payment gateway test cases confirm that every transaction method completes securely.
How Do QA Teams Test UPI and PhonePe Payments on Flipkart?
QA teams test UPI and PhonePe payments on Flipkart by initiating transactions with valid and invalid UPI IDs. Invalid UPI IDs trigger a validation error before the payment intent reaches the bank. Flipkart integrates PhonePe as its primary UPI payment method. UPI test cases verify VPA validation, payment intent flow, and transaction timeout handling.
What Are the Edge Case Scenarios for Flipkart Payment Testing?
Edge case scenarios for Flipkart payment testing cover payment gateway downtime, network disconnection during payment, partial payment failures, and double-charge prevention.
| Test Case ID | Scenario | Steps | Expected Outcome |
|---|---|---|---|
| PG-001 | Successful UPI payment via PhonePe | 1. Select “PhonePe/UPI” at checkout 2. Enter valid UPI ID 3. Approve payment in UPI app |
Payment is successful. Order confirmation is displayed. |
| PG-002 | Credit card payment | 1. Select “Credit/Debit Card” 2. Enter valid card number, expiry, CVV 3. Complete 3D Secure verification |
Payment is processed. Order is placed successfully. |
| PG-003 | Net banking payment | 1. Select “Net Banking” 2. Choose bank from the list 3. Log in and authorize payment |
Payment is successful via net banking redirect. |
| PG-004 | Flipkart Pay Later | 1. Select “Flipkart Pay Later” at checkout 2. Confirm the pay-later option |
Order is placed on credit. Payment is deferred to the billing cycle. |
| PG-005 | Cash on Delivery (COD) | 1. Select “Cash on Delivery” 2. Confirm the order |
Order is placed. COD label is attached to the shipment. |
| PG-006 | Failed payment with invalid card | 1. Enter an invalid or expired card number 2. Attempt payment |
Error: “Payment failed. Please check your card details.” |
| PG-007 | Price, GST, and shipping accuracy | 1. Add products to cart 2. Proceed to payment 3. Verify itemized pricing |
Product price, GST, and shipping charges match the order summary. |
| PG-008 | Payment refund after cancellation | 1. Place and pay for an order 2. Cancel the order 3. Check refund status |
Refund is initiated. Amount is credited within 5-7 business days. |
| PG-009 | Payment during gateway downtime | 1. Attempt checkout when payment gateway is unavailable | Error message is displayed. Alternate payment methods are suggested. |
| PG-010 | Network disconnection during payment | 1. Start a payment 2. Disconnect the network mid-transaction 3. Reconnect and check order status |
Transaction is either completed or rolled back. No duplicate charge occurs. |
Payment testing covers every transaction path on Flipkart. The next section maps all test areas into one end-to-end scenario.
What Is the End-to-End Test Scenario for Flipkart?
The end-to-end test scenario for Flipkart covers a complete user journey across 10 steps.
- Launch the Flipkart app
- Login via OTP
- Search for a product
- Apply filters
- Open the product page
- Add the product to cart
- Apply coupon or SuperCoin discount
- Select delivery address at checkout
- Complete payment via PhonePe UPI
- Verify order confirmation and tracking
End-to-end testing validates that all 8 functional areas work together without data loss or process interruption.
1. Open Flipkart app → 2. Login via OTP → 3. Search “iPhone 16” → 4. Apply brand filter → 5. Open product page → 6. Add to cart → 7. Apply SuperCoin discount → 8. Select delivery address → 9. Pay via PhonePe UPI → 10. Verify order confirmation and tracking
Each step depends on the previous step’s output. Login failure blocks search. Cart errors block checkout. Payment failure blocks order confirmation. End-to-end testing catches integration defects that individual test cases miss.
| Step | Action | Input | Expected Outcome |
|---|---|---|---|
| 1 | Open Flipkart app | Tap Flipkart icon | Homepage loads within 3 seconds |
| 2 | Login via OTP | Mobile: 9876543210 | OTP received. User lands on homepage. |
| 3 | Search product | Keyword: “iPhone 16” | Search results display iPhone 16 listings. |
| 4 | Apply brand filter | Select “Apple” | Results show only Apple products. |
| 5 | Open product page | Click first result | Product page loads with title, price, images. |
| 6 | Add to cart | Click “Add to Cart” | Cart count increments to 1. |
| 7 | Apply SuperCoin discount | Select “Use SuperCoins” | Discount applied. Total price reduced. |
| 8 | Select delivery address | Choose saved address | Delivery date displayed for selected pincode. |
| 9 | Pay via PhonePe UPI | UPI ID: user@ybl | Payment approved. Transaction ID generated. |
| 10 | Verify confirmation | Check order status | Order ID displayed. Confirmation email received. |
QA teams execute this scenario across 3 platforms: Flipkart Android app, Flipkart iOS app, and Flipkart web. Each platform produces different rendering behavior and interaction patterns.
The end-to-end scenario validates full integration. The next section explains how to write test cases for Flipkart in the correct format.
How Do QA Teams Write Test Cases for Flipkart?
QA teams write test cases for Flipkart using a 4-column format: Test Case ID, Scenario, Steps, and Expected Outcome. This structure follows the IEEE 829 test case documentation standard. Each test case targets one specific behavior. The format ensures that any tester can execute the test case without additional context.
What Is the Test Case Format for Flipkart?
The test case format for Flipkart includes 4 required fields and 3 optional fields.
Required fields:
- Test Case ID: Unique identifier (e.g., FL-001, FS-003)
- Scenario: One-sentence description of the behavior being tested
- Steps: Numbered sequence of actions the tester performs
- Expected Outcome: The result the system produces when the test passes
Optional fields:
- Priority: Critical, High, Medium, Low
- Precondition: System state required before execution (e.g., “User is logged in”)
- Actual Result: Recorded during test execution
What Is the Test Strategy for Testing Flipkart?
The test strategy for testing Flipkart combines functional testing, performance testing, security testing, and compatibility testing.
| Testing Type | Flipkart Application | Tools |
|---|---|---|
| Functional testing | Login, search, cart, checkout, payment flows | Manual testing, Selenium, Appium |
| Performance testing | Page load time, Big Billion Days traffic simulation | JMeter, Gatling, k6 |
| Security testing | Payment data encryption, OTP security, session hijacking | OWASP ZAP, Burp Suite |
| Compatibility testing | Android, iOS, Chrome, Firefox, Safari, Edge | BrowserStack, Sauce Labs |
Test strategy defines the testing approach. The challenges that follow define the obstacles QA teams face when testing Flipkart at scale.
What Are the Challenges of Testing Flipkart?
QA teams face 3 primary challenges when testing Flipkart: traffic spikes during sale events, device fragmentation across the Indian market, and rapid feature deployment cycles. Each challenge requires a specific testing approach. Ignoring these challenges produces test suites that miss critical defects during peak usage periods.
How Does Big Billion Days Traffic Affect Flipkart Testing?
Big Billion Days traffic affects Flipkart testing by increasing concurrent user load by 10x to 50x compared to normal traffic levels.
Flipkart’s Big Billion Days sale generates millions of simultaneous transactions. QA teams simulate this traffic using performance testing tools (JMeter, Gatling). Load test scripts replicate the user journey: search, add to cart, checkout, and payment. Performance thresholds define pass/fail criteria: page load under 3 seconds and transaction completion under 10 seconds under peak load.
How Do QA Teams Handle Device Fragmentation for Flipkart?
QA teams handle device fragmentation for Flipkart by testing on the top 20 Android devices that represent 80% of the Indian user base.
India’s mobile market includes thousands of device models across 10+ Android versions. Android versions below 10 still represent a significant share of Flipkart’s user base in tier-2 and tier-3 cities. QA teams prioritize testing on budget and mid-range devices (Redmi, Realme, Samsung M series) because these devices represent the highest traffic volume.
Device cloud platforms (BrowserStack, Sauce Labs) provide access to 200+ real devices for parallel test execution.
These challenges shape how QA teams structure their Flipkart automation, accessibility, and API testing efforts.
How Do Teams Automate Flipkart Test Cases with Selenium?
Teams automate Flipkart test cases with Selenium by writing WebDriver scripts that target Flipkart’s search bar, product listings, cart, and checkout elements. Selenium automates the browser-based web version of Flipkart. Appium automates the Flipkart Android and iOS mobile applications.
What Flipkart Test Cases Are Best for Automation?
Flipkart test cases best for automation are high-frequency regression scenarios with stable UI elements.
- Search and filter validation: Runs on every build to verify search result accuracy
- Cart operations: Add, update quantity, remove, apply coupon
- Checkout flow: Address selection, payment method, order placement
- Login flow: OTP request and email-based authentication
Exploratory testing, usability evaluation, and visual inspection remain manual disciplines. These scenarios require human judgment that automation cannot replicate.
Basic Selenium script for Flipkart search:
WebDriver driver = new ChromeDriver();
driver.get("https://www.flipkart.com");
// Close login popup if present
List<WebElement> closeBtn = driver.findElements(
By.xpath("//button[contains(text(),'\u2715')]"));
if (!closeBtn.isEmpty()) closeBtn.get(0).click();
// Search for a product
WebElement searchBox = driver.findElement(
By.name("q"));
searchBox.sendKeys("iPhone 16");
searchBox.submit();
// Verify search results loaded
// Note: Flipkart uses obfuscated class names that
// change per deployment. Use data attributes or
// XPath with text content for stable locators.
WebElement resultTitle = driver.findElement(
By.xpath("//div[contains(text(),'iPhone 16')]"));
Assert.assertTrue(resultTitle.isDisplayed());
driver.quit();
What Are the Accessibility Test Cases for Flipkart?
Accessibility test cases for Flipkart verify that users with visual, motor, and cognitive disabilities can navigate and complete purchases on the platform. Accessibility testing ensures that screen readers, keyboard navigation, and assistive technologies work across all critical flows.
How Does Screen Reader Testing Work on Flipkart?
Screen reader testing on Flipkart verifies that TalkBack (Android) and VoiceOver (iOS) read product names, prices, and action buttons in the correct sequence.
QA teams navigate the complete purchase flow using only the screen reader. Every interactive element requires an accessible label. Missing labels block screen reader users from completing their purchase.
What Are the API Test Cases for Flipkart?
API test cases for Flipkart validate that search, cart, checkout, and payment APIs return correct data, handle errors, and respond within performance thresholds. API testing verifies the backend independently from the UI. Flipkart’s microservices architecture exposes APIs for each functional area: product catalog, user authentication, cart management, order processing, and payment.
How Do Teams Validate Flipkart Search and Cart APIs?
Teams validate Flipkart search and cart APIs by sending HTTP requests with valid and invalid parameters and asserting response codes, response body structure, and data accuracy.
- Search API: Validate that keyword input returns matching products in JSON format with correct fields (product ID, title, price, image URL)
- Cart API: Validate add, update, and remove operations return the correct cart state with accurate pricing
- Authentication API: Validate OTP generation and verification endpoints with rate limiting and expiration logic
- Payment API: Validate transaction initiation, status polling, and refund processing endpoints
How Does Flipkart Testing Connect to the Full QA Strategy?
Flipkart test cases cover one application. QA teams working on ecommerce platforms test across multiple applications, environments, and release cycles simultaneously. A complete QA strategy for ecommerce combines the functional test cases described in this guide with performance testing during sale events, security testing for payment flows, and automation testing for regression suites that run on every build.
Ecommerce platforms like Flipkart require specialized ecommerce testing because the user journey crosses multiple integrated systems: product catalog, cart engine, payment gateway, logistics, and notification services. A defect in any one system breaks the purchase flow for all users.
Regression automation reduces the manual effort of re-executing 100+ Flipkart test cases after every deployment. Teams that integrate automation testing into their CI/CD pipeline catch regressions within minutes of code merge instead of days into the next manual test cycle.
Sale-event traffic on Flipkart reaches 10x to 50x normal load during Big Billion Days. Teams that run load and performance testing before these events identify bottlenecks in search, cart, and payment services before real users hit them.
How Do QA Teams Report Bugs Found on Flipkart?
QA teams report bugs found on Flipkart using a structured bug report format with 7 fields: title, severity, steps to reproduce, expected result, actual result, environment, and screenshots.
Bug report format:
| Field | Example |
|---|---|
| Title | Cart total does not update after removing a product |
| Severity | High (affects purchase flow) |
| Steps to Reproduce | 1. Add 2 products to cart 2. Remove 1 product 3. Observe cart total |
| Expected Result | Cart total reflects the price of the remaining product |
| Actual Result | Cart total still shows the sum of both products |
| Environment | Flipkart Android app v4.5.2, Android 14, Pixel 8 |
| Attachment | Screenshot of the cart showing incorrect total |
Frequently Asked Questions About Flipkart Test Cases
What Test Cases Cover Flipkart’s Big Billion Days Sale Event?
Big Billion Days test cases cover flash sale timer accuracy, stock depletion under concurrent load, cart expiry after 10 minutes of inactivity, coupon stacking restrictions, and payment queue processing at peak checkout volume.
What Are the Test Cases for Flipkart’s Order Return and Refund Flow?
Return and refund test cases cover return eligibility by product category, pickup scheduling, refund to original payment method, partial return from multi-item orders, and replacement shipment tracking.
What Negative Test Cases Apply to Flipkart’s Coupon and Discount System?
Negative coupon test cases cover expired codes, minimum cart value violations, duplicate application attempts, category-restricted coupons, and SuperCoin stacking conflicts.
How Do QA Teams Test Flipkart’s Pincode-Based Delivery Estimation?
Pincode delivery test cases cover valid pincode estimation, unserviceable pincode errors, express delivery eligibility by metro city, COD availability by location, and delivery date updates on pincode change.
Where Can QA Teams Download Flipkart Test Cases in Excel?
The free Excel sheet with 100+ Flipkart test cases is available for download at the top of this page.
22 Jul 2022
