Run and observe
Real logic and real traffic
Run test cases with every system answering through its real logic, and compare the flows you designed with the calls a running app makes.
Open Flows in the appTwo ways to prove a flow
A flow can pass its test cases and still fail in practice. Two modes close that gap:
- Real logic runs your test cases with every system answering through its own logic, and checks every contract on the way.
- Real traffic compares the flow you designed with the calls a real app made.
Both work on the systems in your organization or project. Neither calls your real APIs.
Test data and Real logic
The Test panel of a flow (press Test in its bar) has two buttons next to Calls answered by:
Test data is the default. Pick Real logic, then run test cases as usual. Each run records which mode it used, and the run history says "test data" or "real logic". See Test cases and runs.
What stops a real logic run
In Real logic mode a run stops at the first call that can't be answered properly:
Click Why? after a failed run to see where it stopped. Databases and queues still answer from their test data, so you don't need logic for them.
For example, a checkout flow can pass with Test data and stop with NO_PROVIDER_LOGIC with Real logic, because Payment Service has no logic yet. That tells you what is left to build.
Check what a flow writes
A test case can also check what the flow writes to a database or a queue. In the test case editor, add a row under Database & queue expectations, such as orders.insert with status equals "paid". Writes are recorded during the run, so the test case fails when the write is missing or wrong.
Real traffic
Real traffic starts from what really happened. When a frontend runs the contract watcher, its calls are reported to Rabbinatix. Each batch of calls is recorded on every flow that makes one of those calls.
To see them, right-click the empty flow canvas and pick Real traffic. The menu shows how many recorded calls the flow has. Each recording shows:
- where it came from, such as the Web App contract watcher, and when; a call made from a screen exported from Rabbinatix says which screen;
- a timeline with one bar per call: its time, status and retries;
- Designed vs actual path, with the systems in your Design next to the Runtime calls.
On the runtime side, a call marked not in design is one your flow doesn't have, such as a retry after a 504. A system marked missing is in your design but wasn't called.
Turn recorded calls into a flow
Turn recorded calls into a draft flow turns recorded calls into a starting point. It creates a draft event logic with a Call Contract step for each API the first system called, and a draft flow around it. Use it when the running app does something your design doesn't describe yet. You need permission to edit flows.
What is not available
- Real logic doesn't call real HTTP APIs. It runs only against the logic in your organization or project.
- Recorded calls come from the contract watcher in development. Importing OpenTelemetry traces from production is planned.
- Per-environment secrets for runs and exporting test cases as test code are not available.
Related
- Test cases and runsWrite test cases as acceptance tests, run the flow and watch it move through your systems, step back in time, and compare runs and versions.
- FlowsBuild a flow from the logic it starts at, see it cross your systems in lanes, and move it from draft to verified.
- Contract watcherDownload one file, start it in your frontend in development, and every real API call is checked against your contracts.
- LogicBuild what a system does by connecting nodes on a canvas: endpoint logic for an API, event logic for a user action, and functions you reuse.
