Automate
Test Automation
Automated business process tests, so every release can be regression tested without stopping the business.
Every release carries the same question: will the business processes that ran yesterday still run tomorrow. Answering it by hand means pulling key users off their jobs for a week. Automated regression answers it overnight instead.
We build automated business process tests. End to end, across the applications a process actually touches, in the order the business runs them.
When you need this
- A release, a support pack or an S/4HANA migration is coming, and the regression test is still a spreadsheet and a room full of key users.
- Testing is the reason go-live dates move.
- Tests exist, but they were built around screens rather than processes, and every release breaks half of them.
What we do
- Pick the regression set. Not everything needs automating. We work with you to identify the business processes whose failure would actually stop the business, and start there.
- Automate end to end. A process rarely lives in one system. Tests follow it across SAP and the applications around it, including the steps that happen outside it.
- Build for change. Tests are structured so a screen change is one update in one place rather than a rewrite. That is the difference between a suite that lasts three releases and one that lasts for years.
- Run unattended. Suites run overnight with zero-touch execution, so the results are waiting in the morning instead of being produced during the day.
- Report so a decision can be made. A pass count tells a release manager nothing. Reporting is by business process, so the go-live decision has something to stand on.
- Take key users out of the execution. They review results and own the process. They stop being the engine of the test cycle.
We work with Worksoft, Tricentis Tosca and UiPath, and we are certified in the tools we use; our consultants are ISTQB certified as well. We stay tool-agnostic on purpose: if you already own a license, we work with it rather than around it. The tool matters less than what is automated and how well it survives the next change to the system.
Tools
These are the tools we work with on this service. Tooling follows the process, not the other way around.
- Worksoft
- Tricentis Tosca
- UiPath
Getting started
How it starts
An engagement starts small and free, and only grows if it earns it.
Free assessment
Two weeks, one process or one regression suite. You get a short written assessment: what we found, what we would change first, and what it would take. No cost, no obligation.
Discovery
We sit with your subject matter experts and functional consultants and map the process as it runs, not as the documentation describes it. Where the data allows it, process mining does the arguing.
Free proof of concept
We take one process and automate it, or put one regression set under automation, and run it on your landscape. You see the result before anything larger is agreed.
Insights
Related insights
Eracons becomes a UiPath partner
Eracons is now a UiPath partner and reseller, widening what we can offer across process automation and enterprise test automation.
Read more
Agentic AI: Are We About to Witness the Birth of a New Testing Industry?
AI agents interpret, choose and act. Validating behavior that is not fully deterministic looks like the beginning of a new testing discipline.
Read more
The impact of SAP test automation on end user experience
Test automation is usually sold as a cost case. Its clearest effect is on the people who use SAP every day.
Read more
Start here
Start with one process and a free assessment.
Pick one process or one regression suite and give us two weeks. You get a short written assessment of what we found and what we would change first — and you decide whether anything follows it.