Test every process in hours, not weeks.
SAP Cloud ERP changes twice a year, and your business changes more often than that. Testing by hand can't keep up: it takes your best people away from their jobs, and it still misses things. We automate the tests for your key processes with SAP's own tools, so every upgrade and every change is checked the same way, in hours.
Different tests, different people, different tools.
A cloud ERP project runs four kinds of tests, and the last one never stops. Automation pays off most there, because the same tests run again with every upgrade and every change, for as long as you run SAP.
| Test | What it proves | When | Who |
|---|---|---|---|
| Unit and role tests | Each configured step works, and each business role can do its job. | During the build | Our consultants |
| End-to-end tests | Whole processes work across modules, integrations and migrated data. | Before acceptance | Our consultants, with your key users |
| User acceptance | The people who'll use the system agree that it works for them. SAP makes this mandatory before go-live. | Before go-live | Your key users |
| Regression tests | What worked yesterday still works after an upgrade or a change. | Every release, every change | Automated, checked by us |
SAP's test tool is already in your system.
SAP Cloud ERP includes a test automation tool at no extra cost. It runs your processes through the real screens with test users, in your test system, and records every step with screenshots. SAP provides ready-made tests that match its standard processes.
We copy those tests and adapt them to your setup: your company codes, your custom fields, your approvals and your data. We record extra steps where you've extended a process, and add checks so a test proves the right result, not just that a screen opened.
Start where a failure would hurt most.
You don't need to automate everything. A focused set of tests on the processes that move money, goods and tax covers most of the risk. We usually start with these, then add more each release.
Sell, deliver, invoice, collect
Orders with your pricing and credit checks, deliveries, invoices with VAT, and incoming payments.
Buy, receive, pay
Requisitions and approvals, purchase orders, goods receipts, supplier invoices and the payment run.
Close the month
Journal entries, accruals, depreciation, foreign currency valuation and the period-end steps.
Plan and make
Planning runs, production orders, confirmations and goods movements for manufacturers.
Tax and banks
VAT invoice output, withholding tax, and payment files for each of your banks.
The right access
Key roles can still do their work, and can't do what they shouldn't, after every role change.
Some processes cross systems. So should the tests.
SAP's built-in tool tests processes inside SAP Cloud ERP. When a process starts in Salesforce, passes through SAP and ends at your bank, the test has to follow it. For that, SAP offers Tricentis test automation through its partnership with Tricentis, connected to SAP Cloud ALM. We use it for the end-to-end flows that matter most.
- Salesforce: deal marked won.
- SAP Cloud ERP: order, delivery, invoice.
- Tax system: invoice accepted.
- Bank: payment matched.
- One automated test checks every hand-over.
Acceptance testing your people can actually finish.
Acceptance testing is where projects slip: testers don't know what to test, results live in spreadsheets, and nobody can say when it's done. We run it in SAP Cloud ALM, which comes with your subscription. Each tester gets their own cases for their role, step by step, and everyone sees progress in one place.
Every failed step becomes a tracked defect, fixed and retested before sign-off. The record stays with your project for auditors and for the next change.
Good tests need good test data.
Most failed automated tests aren't SAP problems. They're missing test data: a customer without a credit limit, a material with no stock, a supplier whose bank details changed. We set up test data that's realistic for Sri Lanka, with valid TIN formats, LKR prices and your real organisation, and keep it in reusable test data sets.
When you need production-like data in the test system, SAP offers a paid test data refresh that copies production data across and anonymises personal details. We help you decide whether it's worth it.
Reusable data sets
Customers, products and suppliers that every test can use, kept apart from real business.
Test users
Users with the right roles for each test, including integration users for interfaces.
Local formats
Valid TIN and VAT numbers, LKR amounts and Sri Lankan addresses, so local checks run too.
No personal data
Test data contains no real employee or customer details unless anonymised.
A test pack that keeps working.
Automated tests are software. They need to be maintained as your processes and SAP change, or they quietly stop proving anything.
Test catalogue
Which processes are covered, which aren't, and why.
Updated every release
Tests reviewed and repaired before each upgrade's test window opens.
Added with every change
A new extension or process doesn't go live without its test.
Results you can read
A short report after each run: what passed, what failed and why.
SAP's post-upgrade tests
Set up so SAP runs its own checks on your system after each upgrade.
Your team trained
Key users can run tests and read results without us.
See it from SAP.
Videos from SAP’s official Services and Support channel on testing with SAP Cloud ALM.
Published by SAP on its official YouTube channels.
© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice
Straight answers.
Do we have to pay for the test tool?
No. SAP's test automation tool and SAP Cloud ALM come with SAP Cloud ERP. Tricentis test automation for cross-system tests is offered through SAP's partnership with Tricentis; we check what your SAP support agreement includes.
How many tests do we need?
Fewer than you'd think. A few dozen well-chosen tests on your main processes cover most of the risk. We start there and add tests as you change the system.
Does automation replace our key users' testing?
No. Automated tests check that processes still work. Key users still review what only a person can judge, such as a form layout or a new screen, and they still sign off acceptance testing.
We're already live without automated tests. Can we start now?
Yes. We start with the processes that hurt most if they fail, have them ready before your next upgrade, and build from there.
Can the tests run in production?
No. Tests run in your test system, so they never create real orders, postings or payments.
Be ready before the next upgrade.
In one session, we look at your processes and your last upgrade, and propose the first set of tests to automate, with the effort and the time it saves your team.
- Processes that matter most
- Built-in tool or cross-system
- Test data and test users
- Acceptance testing in Cloud ALM
- Upkeep every release
SAP, SAP Cloud ALM and SAP Cloud ERP are trademarks of SAP SE. Tricentis is a trademark of Tricentis. Screens shown are illustrations.
Our Orswick Relay is the name we give to how we handle SAP Test Automation: one accountable partner, from the first meeting to long after go-live.