Tosca scripts break with every transport, and manual UAT drags on for weeks per cycle. Coasty runs your test cases from plain-English steps across SAP GUI, Fiori, and the PI, GIS, and portal systems scripted tools cannot reach, and hands back an evidence pack for every case.
0
scripts to rebuild after a transport
Scripted tools like Tosca bind to screen structure, so each transport, Fiori refresh, or MDG change sends someone back into the model to repair broken steps. The systems around SAP (PI middleware, GIS, customer portals) usually fall outside that model, so those end-to-end paths get covered by hand. The result is a UAT cycle that runs for weeks and a maintenance backlog that grows faster than your coverage.
- 01
Write cases in plain English
Describe each test case the way you would brief a tester: log into S/4, run VA01, confirm the outbound IDoc posts. No object maps, no recorded scripts, no code to version.
- 02
Coasty drives the systems
The agent operates SAP GUI, Fiori, and the connected PI, GIS, and portal screens by sight, the same way a person at the keyboard would. When a transport moves a field, it adapts to the new screen instead of failing on it.
- 03
Approve, run, and capture
Sensitive steps pause at a human-approval gate before they execute. Every step is recorded as a timestamped screenshot and assembled into an evidence pack you can hand to the business or an auditor.
Computer-use evals and real-world environments.
© 2026 Coasty
Backed byYCombinator