What is test data readiness?

A check, run before a test cycle starts, that the data every test case needs exists, is consistent across the ERP and its satellite systems, and matches the business rules the test assumes. It turns “data defects” — the largest category of end-to-end test failures in ERP programmes — into findings fixed before execution.

How is this different from test data management tools?

Test data management tools provision or mask data. Test data readiness starts from the business requirement behind each test case, checks the real records across systems, and fixes what is missing under governance. It works with the test management and defect tools you already run.

Do we need to change our test tooling?

No. The readiness check reads test cases from qTest or your tool and reports in a form your defect process (Jira or similar) can use. Corrections go through vise Data Run into SAP via standard interfaces.

What does the roundtable cover?

A 45-minute online discussion for quality-engineering and programme leads, six to eight people, no product pitch: how others keep data from stalling test cycles, what a readiness check finds, and what to do with the findings.

Test Data Readiness · new in 2026 · available for programmes from 2027

Ready on day minus one.

Most end-to-end test defects aren’t process defects. They’re data. We check the data every test needs — across the ERP and the systems around it — before execution starts, so the cycle runs on tests, not on re-loads.

Book a 30-minute call Join the Roundtable ↓

Test run · Day one5 tests · 4 failed on data

Test	Result	Issue
Create sales order	Failed	Customer not found in CRM
Delivery & picking	Failed	Material not extended to plant 1200
Goods receipt	Passed	—
Pricing	Failed	No price condition for this customer
Stock transfer	Failed	Storage location missing in WMS

01 · The problem

Scripts ready. Automation ready. Teams ready. Then the data isn’t.

Large ERP programmes stall when records are missing, inconsistent across systems, or contradict the business rules a test assumes. Each failure gets investigated as a defect, re-run and re-loaded — and the cycle slips. The customer is not in CRM. The material is not extended to the plant. The price condition does not exist. None of that is a process bug, and all of it blocks the test.

02 · How it works

Start from the business requirement — not from the data.

01Start from the requirementEvery test case traces back to a business requirement from design and build — and that requirement defines the data the test needs. AI reads the test case and identifies the business objects, volumes and variants it depends on.
02Check it across systemsAvailability, cross-system consistency (S/4HANA and the satellites: CRM, MES, WMS, data warehouse) and alignment with the business rules the test assumes — days before the cycle starts, not on day one.
03Fix it under governanceWhen a test still fails on data, AI prepares the correction, a person approves it, and vise Data Run applies it with a backup and a full audit trail. AI proposes. People decide. Every change is traceable.

03 · Fit

Not tied to one toolset.

The check works alongside what you already run — mainly SAP, ECC to S/4HANA, and other ERPs such as Business Central — and reads test cases and writes findings where your teams already work.

Test management: qTest — or your tool
Defects: Jira — or your tool
ERP: SAP S/4HANA, SAP ECC, Microsoft Dynamics 365 Business Central
Satellite systems: CRM, MES, WMS, data warehouse

Built on long-term enterprise work.

Global brewing groupIn production for years across operating companies in many countries, with the test team using qTest daily.
European energy operatorSelected in a public data-quality tender ahead of two global DQ vendors.
16 years of SAP data workMigrations, data quality and governed changes on multi-country programmes in Poland, Central Europe and the DACH region.

04 · FAQ

Questions we get.

01What is test data readiness?: A check, run before a test cycle starts, that the data every test case needs exists, is consistent across the ERP and its satellite systems, and matches the business rules the test assumes. It turns “data defects” — the largest category of end-to-end test failures in ERP programmes — into findings fixed before execution.
02How is this different from test data management tools?: Test data management tools provision or mask data. Test data readiness starts from the business requirement behind each test case, checks the real records across systems, and fixes what is missing under governance. It works with the test management and defect tools you already run.
03Do we need to change our test tooling?: No. The readiness check reads test cases from qTest or your tool and reports in a form your defect process (Jira or similar) can use. Corrections go through vise Data Run into SAP via standard interfaces.
04What does the roundtable cover?: A 45-minute online discussion for quality-engineering and programme leads, six to eight people, no product pitch: how others keep data from stalling test cycles, what a readiness check finds, and what to do with the findings.

Two ways to start

Planning an ERP wave or a major test cycle in 2027?

30-minute conversation

Your landscape, your next cycle, and what a readiness check would find in your data.

Test Data Readiness Roundtable

Online discussion for quality-engineering and programme leads. 45 minutes, 6–8 people, no product pitch. First session in December 2026 — the date goes to everyone who signs up.