Lesson 4 of 7
Tools and the system of record
9 min
Listen to this lesson
A TCoE standardizes its tools for the same reason it standardizes evidence: so that results from every project and release can be compared, audited and reused. That needs one system of record for tests, results and defects, a short list of approved tools around it, and an owner for each tool. Tools follow the operating model, never the other way round.
SAP's own tools for testing
| Tool | What it gives a TCoE | Watch out for |
|---|---|---|
| SAP Cloud ALM | Test Preparation for test cases built from process activities; Test Plans for cycles (preparation, execution, completion); Test Execution for step results and defects raised from the run; the Defects app; analytics with requirements traceability; a Quality Gates app; Joule agents (in Early Adopter Care) that propose test scope, generate draft manual test cases and list the test data a case needs | Set up scope and the process hierarchy first; test cases hang off them |
| Test Automation Tool (Public Edition) | Standard automates that match SAP's test scripts in SAP Signavio Process Navigator, custom automates, and Post-Upgrade Tests that SAP runs with consent; results are visible in SAP Cloud ALM | Customized processes need updated or custom automates |
| SAP Cloud ALM Test Automation API | A published interface that an external test tool implements so that Cloud ALM can synchronize its test cases, read data variants, trigger runs, check job status and fetch execution history; the run itself happens in the tool | Check that a candidate tool implements it, or is one of the providers SAP integrates directly, before you choose it |
| SAP Solution Manager 7.2 | Test Suite and change control (ChaRM) for existing on-premise landscapes | Mainstream maintenance ends at the end of 2027; SAP advises moving to SAP Cloud ALM before then |
| eCATT | Scripted tests and test data creation inside the ABAP stack of Private Edition and on-premise systems | Needs technical skills; keep scripts tied to the regression design |
SAP tools a TCoE is likely to meet. Features change often, so check SAP Help for your SAP Cloud ALM tenant.
Contoso's landscape shows the typical split. The ECC support team still runs ChaRM on SAP Solution Manager 7.2 for ED1, EQ1 and EP1, while the S/4HANA program runs in SAP Cloud ALM. The TCoE's tool standard names SAP Cloud ALM as the system of record for S/4HANA tests and defects, moves only the ECC test cases that still describe a live process, and retires the rest with the ECC systems. Extended maintenance for Solution Manager 7.2 to the end of 2030 covers only selected scenarios, including the Test Suite and change control, and SAP includes it at no extra cost for customers who take SAP Business Suite 7 extended maintenance; check the terms in your own contract. Either way it is a bridge, not a destination.
Choosing and introducing a tool
- Start from requirements: the processes and UI technologies you must test (SAP Fiori apps, SAP GUI transactions, APIs and IDocs) and how results must reach the system of record.
- Evaluate against objective criteria, including the vendor or community behind the tool, licensing models and the training your people will need.
- Prove it on your system: a proof of concept on a real Contoso process in CMQ, then a pilot on one release before any wider roll-out.
- Write usage guidelines, adapt processes where needed, and roll out in increments.
- Name a tool owner who decides naming, storage and access, and an administrator who keeps the tool running.
Return on investment
CTAL-TM makes the test manager responsible for the ROI case. Count non-recurring costs (requirements, evaluation, proof of concept, purchase or build, guidelines, initial training, integration) and recurring costs (licenses and support, script maintenance, ongoing training), plus the opportunity cost of time spent on the tool instead of on testing. Set them against benefits you can measure: fewer manual regression hours, shorter cycle time, more coverage. Contoso's case rested on its own numbers, a regression cycle falling from about 1,400 hours to about 700 as automation and data recipes matured, not on a vendor's benchmark.
What would you do?
Two Contoso teams each want a different automation tool for Fiori regression, and both have run a convincing demo. What should the TCoE lead do?
- Name one system of record for tests, results and defects; for Contoso it is SAP Cloud ALM.
- Know SAP's tools and their limits, including the end of mainstream maintenance for Solution Manager 7.2 in 2027.
- Introduce tools with requirements, a proof of concept, a pilot and a named owner.
- Own the ROI: non-recurring, recurring and opportunity costs against measured benefits.
Check your understanding · not graded
Lesson check
1. Which SAP Cloud ALM app records step results and lets a tester create a defect straight from the test run?
2. When does mainstream maintenance for SAP Solution Manager 7.2 end?
3. Which cost belongs to the non-recurring cost of a new test automation tool?
4. Why keep test logic readable in the system of record rather than only inside automated scripts?