DeviQA and Soapbox: WMS functional testing case analysed

Verdict: what is checkable

Client profile as published

Client

Soapbox

Segment

Ecommerce and D2C (direct to consumer: a brand that sells its own products online to shoppers without a retailer in between.)

Region

not stated in the source

Channels

ecommerce

Size indicators

none given

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

Systems in scope

• WMS (warehouse management system: software that runs receiving, storage, picking and shipping inside a distribution center.): named in the title and the About project section ("e-commerce fulfillment and warehouse management platform")
• OMS (order management system: software that routes, splits and tracks customer orders across stores, warehouses and carriers.): named in the About project section ("order processing")

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

Problem as stated

Before the engagement Soapbox ran tests by hand, test coverage stood at 40%, a regression run took about 1.5 weeks and stories took about two weeks to move forward. The page describes the QA process as poor and the Android app code as carrying many major and critical issues. Soapbox asked DeviQA to structure test documentation, widen coverage and cut testing time on the web platform and the Android app prototype. [ev-0891]

A huge amount of major/critical issues in the code base of the mobile app (quoted from the source)

Approach

Testing types

functional, automation and mobile (main scope: functional)

Team shape

3 manual QA engineers, 1 automation QA engineer, 1 mobile developer

Duration

Since 2021

Engagement model

dedicated-team

Tooling named in the source

Figma, GitLab, GitLab issues, Sentry, Datadog, Android Studio, Cypress, MS Visual Studio Code, Google Docs, Google Sheets, React Native, React Native Reanimated, React Navigation, App Center, Swagger

Metrics claimed

What the case does not say

• Measurement method.
• Duration over which the metric held.
• Cost.
• What was out of scope.

Reading notes for a buyer

This case speaks to the scenario “OMS or WMS replacement” and feeds dimension D2 (Retail system coverage) of the methodology. A question to put to DeviQA:

Which warehouse and order flows did the web coverage figure include, and how was coverage counted? [ev-0891]

Source and verification

Source

QA services for warehouse management software | DeviQA case study

Published

not dated by the vendor

Verified

2026-10-30

Evidence grade

secondary

Corroborating sources

none found

Vendor profile: DeviQA. System facet: OMS and WMS testing vendors.