How the Sjtubtool works in practice
The Sjtubtool is built on Azure API Management and the Microsoft Power Platform, using Dataverse, Power Automate and a model-drivenapp. All outbound calls to external partner systems are routed through API Management, where request-level logic determines the execution path. Based on predefined rules and configuration, the API gateway either returns a simulated response or forwards the request to the actual downstream system. This routing happens centrally at the API layer, without requiring changes in the consuming Power Platform solutions, and with negligible impact on runtime behaviour.
Testers define and manage simulated responses through a Power App, where they can configure payloads for specific endpoints, including error conditions and edge cases. Because responses are controlled at the API boundary, tests run in isolation from external systems and behave deterministically: the same input consistently produces the same outcome. Designing this API-level separation was a key architectural choice, ensuring testability without leaking test logic into business flows.
The result is:
- Testing no longer depends on partner availability
- Unusual scenarios can be tested deliberately and repeatedly
- Test sessions become more reliable and easier to plan
The Sjtubtool is now actively used across Obvion and has become part of the standard testing approach. It shortens lead times and removes a familiar source of friction: having to pause testing because an external dependency is unavailable.
And yes, the name Sjtubtool is intentional. Else where you might call it a Stubtool. In Heerlen, Limburg, local flavour applies.
