SAP Quality Engineering, written from experience.
Practical thinking on SAP testing, S/4HANA transformation, automation and assurance — from people who work inside the programmes.
Three worth your time.
Five questions worth answering before SAP go‑live
Traceability, real business coverage, production-like data, a rehearsed cutover and the evidence behind the decision — five questions that tell you more than a pass rate.
9 min read S/4HANAWhat should we re‑test after an SAP upgrade?
Nine areas worth validating after an SAP upgrade, what SAP’s own tools do and do not tell you about each, and how change impact should decide the depth of regression.
10 min read S/4HANAAn S/4HANA upgrade is a business‑process test, not just a technical upgrade
Custom code, business data, interfaces and process behaviour all need attention when the underlying ERP changes beneath them.
4 min readEverything we have written down.
Five questions worth answering before SAP go‑live
Traceability, real business coverage, production-like data, a rehearsed cutover and the evidence behind the decision — five questions that tell you more than a pass rate.
9 min read S/4HANAWhat should we re‑test after an SAP upgrade?
Nine areas worth validating after an SAP upgrade, what SAP’s own tools do and do not tell you about each, and how change impact should decide the depth of regression.
10 min read Executive AssuranceBefore you approve an SAP go‑live, what evidence should be on the table?
Leadership needs visibility into business-process coverage, material defects, unresolved dependencies and the evidence behind readiness — not another status colour.
5 min read S/4HANAAn S/4HANA upgrade is a business‑process test, not just a technical upgrade
Custom code, business data, interfaces and process behaviour all need attention when the underlying ERP changes beneath them.
4 min read SAP TestingFrom requirement to business process: a better way to define SAP test coverage
Meaningful coverage traces what the business expects through processes, variants, scenarios and evidence — not through a total.
4 min read AutomationWhat should you automate first in SAP?
Sustainable automation starts with stable, repeatable and business-critical processes rather than automation-volume targets.
4 min read Executive AssuranceFive quality signals every SAP steering committee should see
Five signals that tell a steering committee something a completion percentage cannot.
4 min read S/4HANABuilding regression into the S/4HANA release rhythm
SAP ships on its own schedule. A regression suite that is rebuilt for each release will always be behind it.
4 min read S/4HANAWhat should testing protect during an ECC‑to‑S/4HANA conversion?
Six things change underneath the business during a conversion. A test strategy is a set of decisions about which of them to protect first.
4 min read AutomationHow a maintained SAP regression suite changes the economics of releases
Automation does not pay back on the day it is built. It pays back on the fourth, fifth and tenth time it runs.
4 min read Field NotesOne business process. Six places quality can disappear.
Source-to-pay, followed all the way through, and the six points at which coverage quietly goes missing.
4 min read AutomationWhere AI can genuinely help SAP test design
Four places AI earns its keep in SAP test design, and the judgement it does not replace.
3 min read Field NotesTesting the hand‑offs: where SAP processes become enterprise processes
Every boundary a process crosses is owned by somebody, and the gaps sit between the owners rather than inside them.
3 min read Executive AssuranceWhat does “ready” actually mean in an SAP programme?
Readiness is a judgement about business capability, made by named people, on evidence. It is not a number that arrives from a tool.
3 min readNothing published under that topic yet.
The work teaches us things. We write some of them down.
New perspectives are published when the work gives us something useful to say.