suxxesso Tool Suite Overview: Live Walkthrough
SAP test automation live means a running system, not a slide deck. In this webinar we build a live SAP test case and run it through to the report. You […]
SAP test automation live means a running system, not a slide deck. In this webinar we build a live SAP test case and run it through to the report. You […]
SAP test automation live means a running system, not a slide deck. In this webinar we build a live SAP test case and run it through to the report. You see Test Pilot, Data Manager, and Test Cockpit working together rather than explained one at a time.
The run spans Fiori and SAP GUI. It pulls real master data instead of maintained lists and ends with a scheduled test plan and its execution log.
Building test cases is the smaller part of the work. The larger part is keeping them alive through every transport, release, and upgrade. That is where many test automation projects fail.
The suxxesso Tool Suite starts with object recognition. A recorded step identifies an SAP screen object by a combination of attributes, not a single one. When a release changes one of those attributes, the test keeps running. You don’t rebuild the test – you reconcile the change. That is test automation built to work outside the demo.
We start with a purchase requisition in Fiori. Test Pilot records the input steps and turns them into an executable script. Materials, vendors, and quantities become variables right in the recording step.
Step two creates the purchase order in SAP GUI, step three posts the goods receipt. The document number from step one passes automatically into the following steps.
The test data comes from Data Manager. It selects fresh master data from the system instead of falling back on maintained lists. Finally, we schedule the test plan in Test Cockpit and open the report with its screen recording.
Test managers, quality engineers, and SAP CoE leads who want a working view of the Tool Suite. No prior knowledge of suxxesso required.
If your business users still walk through every process manually after each update – executing, documenting, reporting – this is the other way: only the change gets reconciled, the rest runs automated.
No. Test Pilot records the steps you already perform in SAP and generates the executable script from them. You add verifications with a click. The people who own the process build the tests – not a development team.
Yes. SAP standard transactions, Fiori apps, and Z-transactions run in the same recording pass. Test Pilot does not distinguish between standard and custom development; it identifies screen objects by their attributes.
Yes, when the tool carries the business users. At paper manufacturer Sappi, more than 700,000 automated test runs completed in 18 months. That saved around 36,000 testing hours. One dedicated person on the business side carried it. Read the full story in our suxxess Stories.
A re-test checks whether a reported defect is fixed. A regression test checks whether a change broke something elsewhere. The ISTQB glossary carries the formal definitions; the webinar shows how the two differ in daily SAP practice.
Sabrina Socaciu · Presales Consultant · suxxesso.
Tuesday, October 20, 2026, 2:00–3:00 PM CEST (1:00 PM BST, 12:00 UTC), online. This webinar is free to attend. Everyone who registers receives the recording, whether or not you join live.
Prefer to see the Tool Suite on your own SAP landscape? Book a demo. More dates are listed in our events calendar. The demo runs on SAP S/4HANA; the product documentation lives on the SAP Help Portal.
You need to load content from reCAPTCHA to submit the form. Please note that doing so will share data with third-party providers.
More Information