GSPANN and an anonymised specialty retailer: IBM Sterling test automation 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 8 metrics, 0 are verifiable yes, 0 partial and 8 no. [ev-0982]
Client profile as published
- Client
A leading US-based retail company that sells high-quality home furnishings and kitchenware.
(the vendor's description; the vendor does not name the client)- Segment
- Specialty retail
- Region
- US
- Channels
- not stated
- Size indicators
billion-dollar retailer
;multiple premium brands
;omnichannel specialty retailer
The client description and size indicators are quoted from the source; segment, region and channels are this site's classification. [ev-0982]
Systems in scope
- OMS (order management system: software that routes, splits and tracks customer orders across stores, warehouses and carriers.) (IBM Sterling OMS): named in the Challenge section
- WMS (warehouse management system: software that runs receiving, storage, picking and shipping inside a distribution center.) (Warehouse Management for Open Systems (WMOS)): named in the Challenge section
- Integrations (Microsoft Dynamics 365, Oracle, Microsoft Azure): named in the Challenge section
Where the source names each system is quoted or summarised from the case page. [ev-0982]
Problem as stated
Releases of the retailer's Microsoft Dynamics 365 workflows were held up by manual testing. Dynamics 365 is tightly linked to IBM Sterling OMS, WMOS, Oracle and Azure, so each release needed end-to-end checks that took 2 to 3 weeks. Each premium brand needed its own repeated cycle. Thin documentation tied testing to a few specialists, and manual errors caused rework and delayed releases. [ev-0982]
every release required extensive end-to-end testing(quoted from the source)
Approach
- Testing types
- automation, api and functional (main scope: automation)
- Team shape
- not stated
- Duration
- not stated
- Engagement model
- not stated
- Tooling named in the source
- Java, Selenium 4, Cucumber 7, JUnit 5, RestAssured 5, Allure Reporting, Report Portal, Azure Portal
Metrics claimed
| Metric | Value | Unit | Claimed by | Verifiable | Evidence |
|---|---|---|---|---|---|
| release cycle time reduction | 90 | % | vendor | no | ev-1571 |
| monthly savings from reduced manual testing effort | $7,000-$10,000 | USD per month | vendor | no | ev-1572 |
| regression testing duration | 5-7 days to just hours | days | vendor | no | ev-1573 |
| manual testing hours saved per month | 140-150 | hours per month | vendor | no | ev-1574 |
| annual savings from reduced error correction and rework | $10,000+ | USD per year | vendor | no | ev-1575 |
| potential annual revenue increase | 5-7 | % | vendor | no | ev-1576 |
| automated test pass rate | 90%+ | % | vendor | no | ev-1577 |
| business-critical scenarios automated | 100+ | scenarios | vendor | no | ev-1578 |
What the case does not say
- Measurement method.
- Duration over which the metric held.
- Team size on both sides.
- Cost.
- What was out of scope.
- Whether the client is still a client.
- Date of the work.
Reading notes for a buyer
This case speaks to the scenario “OMS or WMS replacement” and feeds dimension D4 (Test automation evidence) of the methodology. A question to put to GSPANN:
How were the monthly hours and dollar savings measured, and which automated scenarios run against Sterling OMS and WMOS rather than Dynamics alone? [ev-0982]
Source and verification
- Source
- Dynamics 365 Test Automation Cuts Release Time by 90%
- Published
- not dated by the vendor
- Verified
- 2026-10-30
- Evidence grade
- secondary
- Corroborating sources
- none found
| Id | Claim | Source | Class | Grade | Published | Verified |
|---|---|---|---|---|---|---|
| ev-0982 | Dynamics 365 Test Automation Cuts Release Time by 90% | Dynamics 365 Test Automation Cuts Release Time by 90% | vendor-case-study | secondary | 2026-10-30 | |
| ev-1571 | 90% reduction in release cycle time from 2-3 weeks to 1-2 days | Dynamics 365 Test Automation Cuts Release Time by 90% | Case Study | GSPANN | vendor-case-study | secondary | 2026-10-30 | |
| ev-1572 | $7,000-$10,000 monthly savings through reduced manual testing effort | Dynamics 365 Test Automation Cuts Release Time by 90% | Case Study | GSPANN | vendor-case-study | secondary | 2026-10-30 | |
| ev-1573 | Regression testing compressed from 5-7 days to just hours | Dynamics 365 Test Automation Cuts Release Time by 90% | Case Study | GSPANN | vendor-case-study | secondary | 2026-10-30 | |
| ev-1574 | 140-150 hours per month saved in manual testing activities | Dynamics 365 Test Automation Cuts Release Time by 90% | Case Study | GSPANN | vendor-case-study | secondary | 2026-10-30 | |
| ev-1575 | $10,000+ annual savings from reduced error correction and rework | Dynamics 365 Test Automation Cuts Release Time by 90% | Case Study | GSPANN | vendor-case-study | secondary | 2026-10-30 | |
| ev-1576 | 5-7% potential annual revenue increase through faster time-to-market | Dynamics 365 Test Automation Cuts Release Time by 90% | Case Study | GSPANN | vendor-case-study | secondary | 2026-10-30 | |
| ev-1577 | 90%+ automated test pass rate, ensuring consistent quality delivery | Dynamics 365 Test Automation Cuts Release Time by 90% | Case Study | GSPANN | vendor-case-study | secondary | 2026-10-30 | |
| ev-1578 | Automated 100+ business-critical scenarios across integrated enterprise systems | Dynamics 365 Test Automation Cuts Release Time by 90% | Case Study | GSPANN | vendor-case-study | secondary | 2026-10-30 |
Vendor profile: GSPANN. System facet: OMS and WMS 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 .