QAble and Flipkart: Mobile commerce mobile testing case analysed

Verdict: what is checkable

The evidence grade (this site's label for how a case is sourced: primary with client or press confirmation, secondary when vendor-hosted only.) is secondary: the only source is the vendor's own page; of 4 metrics, 0 are verifiable yes, 4 partial and 0 no. [ev-1721]

Client profile as published

Client
Flipkart
Segment
Marketplace
Region
India
Channels
marketplace, ecommerce and mobile
Size indicators
India's largest e-commerce marketplace

The client description and size indicators are quoted from the source; segment, region and channels are this site's classification. [ev-1721]

Systems in scope

  • Mobile commerce (Flipkart app (Android and iOS), AR/VR and 3D product view): named in the About section and Services item 01 ("all AR/VR interactions within the Flipkart app"); web 3D view on Chrome and Firefox named in the Before/After table

Where the source names each system is quoted or summarised from the case page. [ev-1721]

Problem as stated

Flipkart added an AR and 3D product view to its app so shoppers can place appliances, electronics and beauty products in their own rooms before buying. The feature raised new test problems: surface detection, 3D rendering quality, a wide spread of Android hardware, and consistent behavior under different lighting. The page says there was no existing process for testing AR features. [ev-1721]

No established process for testing AR/VR features (quoted from the source)

Approach

Testing types
functional and mobile (main scope: mobile)
Team shape
Dedicated QA engineers
Duration
not stated
Engagement model
dedicated-team
Tooling named in the source
ARCore, ARKit, BrowserStack, Chrome DevTools, 3D View SDK

Metrics claimed

Metrics as published, with who claims each and what this site could check.
MetricValueUnitClaimed byVerifiableEvidence
real devices validated10+real devicesvendorpartialev-1722
AR frameworks covered2AR frameworksvendorpartialev-1723
product categories tested100%vendorpartialev-1724
bug patterns identified5+bug patternsvendorpartialev-1725

What the case does not say

  • Measurement method.
  • Team size on both sides.
  • Cost.
  • What was out of scope.
  • Date of the work.

Reading notes for a buyer

This case speaks to the scenario “First outsourced QA team for a mid-size retailer” and feeds dimension D1 (Retail case study evidence) of the methodology. A question to put to QAble:

Which devices made up the test matrix, and what recurring AR bug patterns did you find and fix? [ev-1721]

Source and verification

Source
Flipkart AR/VR QA Case Study | QAble
Published
not dated by the vendor
Verified
2026-10-30
Evidence grade
secondary
Corroborating sources
none found
Evidence records for this case.
IdClaimSourceClassGradePublishedVerified
ev-1721AR/VR and 3D view QA for India's largest e-commerce platformFlipkart AR/VR QA Case Study | QAblevendor-case-studysecondary2026-10-30
ev-172210+ Real devices validatedFlipkart AR/VR QA Case Study | QAblevendor-case-studysecondary2026-10-30
ev-17232 AR frameworks coveredFlipkart AR/VR QA Case Study | QAblevendor-case-studysecondary2026-10-30
ev-1724100% Product categories testedFlipkart AR/VR QA Case Study | QAblevendor-case-studysecondary2026-10-30
ev-17255+ Bug patterns identifiedFlipkart AR/VR QA Case Study | QAblevendor-case-studysecondary2026-10-30

Vendor profile: QAble. System facet: Mobile commerce app testing vendors.

Positions on this page are computed from the methodology published at /methodology/ and from the evidence records linked on this page. Case study figures are the vendor's or the client's claims as published at the linked source; the "verifiable" column states what this site could check. The site does not recommend vendors, does not accept paid placement and does not publish rates. Last computed: 2026-11-03.

Published by the editor of retailqavendors.com. Last reviewed .