iGlow / Test with simulation
Guide · Test
Test an SAP CPI iFlow with simulation
Updated · by the iGlow team at StellarClouds
Short answer: iGlow tests in two ways. Before deploy, it runs SAP's own iFlow simulation over the steps and routes it changed, with mocked receivers, so no external system is called. After deploy, the Test tab sends a real message to the iFlow's HTTP endpoint, with the URL, OAuth or Basic auth and CSRF token filled in for you.
Simulation before deploy
- iGlow keeps a list of the steps and routes it changed that no simulation has covered yet, and works through it.
- The simulation follows the route a Router really sends the message down, and runs to the end of the normal route.
- Receivers are mocked with the reply iGlow expects, so no system outside the tenant is called.
- Deploy refuses changed steps that no passing simulation has covered, unless you agree to deploy them untested; it names those steps.
- When SAP refuses to start a simulation, you see all of SAP's reasons.
Test calls after deploy
- Open the Test tab and pick a deployed iFlow with an HTTPS sender.
- Add the service key once. It stays in your browser and is never sent to iGlow's servers or to the AI.
- Start from a sample body: iGlow reads the iFlow's first steps (converters, scripts, Router XPaths, schemas) to choose JSON or XML and the fields. Suggest body asks the AI for a realistic one.
- Click Send. You see the response and the message status; for a failed message, the failing step and error, with a Fix button.
Questions
Can I test an iFlow without calling the real systems?
Yes. SAP's simulation runs steps of an iFlow in design time with mocked receivers. iGlow starts and reads these simulations for you and covers every changed step and route.
Is iGlow's Test tab like Postman?
Yes, for your own iFlows: it fills in the real endpoint URL, gets the OAuth token from your service key and fetches the CSRF token, and then shows the message's status on the tenant.