Four packs, one language
Each pack adds only its platform's verbs. A tester who knows one pack can read the others.
Packaged apps engine
Certify every vendor update before the window closes
Packs for Oracle, SAP, Salesforce and Workday speak your transactions in plain English, and each vendor update shows which tests to run first.
- Ready for every vendor update
- Run affected tests first
- One test across systems
Run transaction 'VA01'
Select 'OR' from 'Order type'
Type '{{customer.sold_to}}' into 'Sold-to party'
Press 'Ctrl+S'
Remember the order number as {{order.id}}
Keep pace with vendor updates
Know what changed
Release-impact intake maps each vendor update to your flows and lists the tests to run first.
Never automated before
Most packaged-app testing is still manual. Business teams can now certify each update in plain English.
How the packs work
Named after your transactions
Steps use the transactions, tasks and records your teams already know.
- SAP: transactions, screens and grids, such as Run transaction 'VA01'
- Oracle: finance, procurement and supply chain flows
- Salesforce: objects, record pages and list views
- Workday: business processes, tasks and approvals
Ready before the window opens
Packaged apps change on the vendor's schedule, with a short window to regression test.
The vendor publishes an update and its release notes.
Intake maps changed areas to the flows and screens you use.
A person reviews the impact list and approves the plan.
Affected tests run and results feed a go decision.
One view of a process
Packs, desktop and data steps in one language give every role the same picture.
- Business testers record a process and read it back as sentences
- QA leads cover custom Windows clients with vision recognition
- Release managers get audit-ready evidence for every check
- Process owners follow an order from CRM to ERP to warehouse as one test
The whole path, one test
An order might start in Salesforce, post in SAP, pass a Windows client and land in a warehouse table.
- The flow sits once in the App Model
- Vendor changes map to the same flows your tests cover
- Results land in Quality View as one record
Questions
Do I need a tool per platform?
No. Every pack uses the same core verbs, so one team and one suite cover all four platforms.
We rely on RSAT today. What should we do?
Microsoft has announced that RSAT support ends on 15 May 2027. Talk to us about moving those flows into plain-English steps.
Does a pack call AI during runs?
No. Pack steps compile to deterministic code like every other step.
Bring one upgrade
Leave with a certification plan
Bring your next Oracle, SAP, Salesforce or Workday update and see which flows it touches.