Noesis and an anonymised omnichannel retailer: POS functional testing case analysed

Verdict: what is checkable

Client profile as published

Client

a global retail group operating in over +90 countries (the vendor's description; the vendor does not name the client)

Segment

Enterprise omnichannel

Region

Europe

Channels

stores

Size indicators

operating in over +90 countries; a diverse portfolio of retail brands across sectors such as food, electronics, and fashion

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

Systems in scope

• POS (point of sale: the till software and hardware that rings up store sales, takes card payments and prints receipts.): named in the Solution section of the vendor PDF (POS Lab Test Factory for POS testing of multiple releases) and in the services list on the page (POS lab setup)

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

Problem as stated

The client wanted its testing turned into one enterprise-wide model that used fewer resources and cost less. The vendor PDF lists the challenges. The testing model had to be reworked to cover the application landscape and to support newer engineering and testing methods. Performance had to be monitored as user adoption grew. Regression and performance testing had to run across 500+ applications, including ERP-based ones. [ev-1634]

Streamline the testing process into an enterprise-wide, resource-efficient, and cost-effective model. (quoted from the source)

Approach

Testing types

functional, automation, performance and security (main scope: functional)

Team shape

Dedicated Test Centre providing testing services in a managed model

Duration

not stated

Engagement model

managed-testing

Tooling named in the source

Microsoft (tool re-evaluations, customisations and integrations), IBM (tool re-evaluations, customisations and integrations)

Metrics claimed

What the case does not say

• Baseline before the engagement.
• Measurement method.
• Duration over which the metric held.
• Team size on both sides.
• Cost.
• Whether the client is still a client.
• Date of the work.

Reading notes for a buyer

This case speaks to the scenario “POS rollout across stores” and feeds dimension D2 (Retail system coverage) of the methodology. A question to put to Noesis:

What was the critical incident count before the managed service started, and over which period was the reduction measured? [ev-1634]

Source and verification

Source

Excellence in Enterprise Testing in the Retail Sector

Published

not dated by the vendor

Verified

2026-10-30

Evidence grade

secondary

Corroborating sources

none found

Vendor profile: Noesis.