Your regression pack is already written. It's just in Excel.
The manual test cases your teams wrote for the migration are the regression pack. AutoTestr drives the live system through each one and hands back Certify automation, with object identity from your own Certify configuration.
- Your workbooksThe manual cases written for the migration
- Your S/4HANA systemFiori, WebGUI, WebDynpro and SAP GUI, driven live
- Your CertifyCapture XML and process-export ZIP, imported and executed
The migration date is set. The regression pack isn't automated.
Regression is on the critical path
Every mock cut-over and every go-live gate asks the same question: do the business processes still work end to end? The answer depends on coverage that has to exist first.
The recorder moves at the speed of people
The cases are written, often hundreds of them. Turning each into automation still needs someone to perform it by hand while it records.
Change keeps coming after go-live
Quarterly releases and the systems around SAP keep moving, so the pack you build for the migration is the pack you keep running.
The SAP technologies in your cases, with their status.
Status words, not adjectives: Built means it is in the product today; Built, not run live means the code exists and has not yet been proven on a live system.
| Technology | How AutoTestr drives it | Status |
|---|---|---|
| SAP Fiori (UI5) | In the browser; elements routed by your Application Preset | Built |
| SAP WebGUI | In the browser; routed per element by your Application Preset | Built |
| SAP WebDynpro | In the browser; routed per element by your Application Preset | Built |
| SAP GUI | Through SAP GUI Scripting, which must be enabled in client and server. Built per case; switching technologies step by step is still to be verified live | Built |
| One case across browser and SAP GUI | A single test case that moves between a browser application and SAP GUI | Built, not run live |
Beyond SAP, XF profiles are included for Salesforce, ServiceNow, Workday, Oracle EBS, Ariba, Hybris, UKG, Concur, SuccessFactors. Those profiles have not yet been run live against those applications, which is why we say “included” rather than “supported”.
Measured against the capture a person made by hand.
- objects identical to the customer's own hand capture
- 17 of 17
- Advance Order
- steps identical to the customer's own hand capture
- 19 of 19
- Advance Order
- identity strings byte-identical to Worksoft's own recorder
- 61 of 62
- reference captures
On Advance Order, the workbook was driven end to end and the result compared with the capture the customer's own team had recorded by hand from the same workbook. The identity strings were compared with reference captures made by Worksoft's recorder. We don't publish time-saved or accuracy figures yet: those get measured on your cases, in the pilot.
Know what converts before you commit.
One week to census every workbook you offer, two weeks to run 20 cases through your own Certify, and a readout with numbers measured on your cases.
Week 0
Prerequisites signed off, agreement in place, success criteria in writing.
Week 1 · Census
Every workbook parsed and classified: what is drivable, gaps per sheet, sizing.
Weeks 2–3 · Pilot
20 cases chosen for variety, imported and executed in your Certify.
Week 4 · Readout
Measured results against your baseline, a scale plan and a price.
Your SAP landscape stays yours.
- The runner that drives SAP sits inside your network, in every edition.
- Credentials never leave the runner; passwords are protected there with Windows DPAPI.
- No language model is used unless a run enables one; the runner kit carries none.
- A Sovereign edition runs the whole control plane inside your network, with your own sign-in and an offline-signed licence.
Start with the census. It is useful on its own.
Send us the workbooks you have. We will tell you, sheet by sheet, what AutoTestr can drive and what each one is missing.
Worksoft and Certify are trademarks of their owner. MindMap AutoTestr is a MindMap Digital product; naming Certify describes the files AutoTestr produces and does not imply endorsement by Worksoft. Capability status words on these pages (Built, Built not run live, Roadmap) describe the current release.