Build behaviour (Flow-Driven Development)
Requirements and coverage
Write requirements, link them to flows and test cases, and see which ones your runs prove. Follow any change to the flows it affects.
Open Requirements in the appWhat a requirement is
A requirement says what the software must do. It has a short title, such as "Reject invalid credentials", and a description that says it in full, such as "The system must reject invalid credentials and never say whether the email exists". On its own it is just text. Linked to flows and test cases, it becomes something a run can prove. Rabbinatix keeps the whole chain: requirement → flow → test case → test data → logic → contract → result.
Each requirement has a key such as REQ-AUTH-001, so you can name it in tickets and commits.
Write one
- Open Requirements under Behaviour in the sidebar.
- Press New requirement. Give it a short name under Title and say what it asks for under Description. The title is required; the description is optional.
- Under Flows, pick the flows that implement it.
- Under Test cases that verify it, tick the test cases that prove it. If you tick none, all test cases of those flows count.
- Press Save.
Store templates bring their requirements with them, already linked.
Coverage
Each requirement shows its coverage, worked out from the latest run of each linked test case:
The numbers at the top of the page count all requirements, those verified (passing), those failing and those not covered.
Open a requirement to see what it's linked to: the flows, test cases, logic and contracts behind it. Press Verify now to run its test cases again. A requirement with no flow can't be verified; Request a flow creates a ticket asking for one. The open requirement also lists related objects and its tickets.
Follow the chain both ways
Every link is stored, so you can start from either end.
- From a flow: the Requirements & coverage panel on the flow page lists what the flow verifies.
- From logic: the Where used tab in the logic editor lists the flows and steps it runs in, the logic that calls it, the requirements those flows verify and its tickets.
- From a system: the system's Flows tab lists every flow that starts in it, calls it, is called by it or reads its data, with each test case's latest result.
- From a failed run: Copy as bug report copies the key, flow, step, test case, expected and actual result, and a link to the run.
- From a key: press
Ctrl+Kand type any key, even a step'sNODE-…key, to open it.
Flow impact
Change impact (Change impact) tells you which contracts a change breaks. Flow impact goes one step further: it tells you which business flows and test cases break.
When you change an API, a field, test data or a shared function, the impact panel lists the Affected flows. A button re-runs their test cases against your unsaved draft, so you learn how many test cases would start failing before you save. In the logic editor, the same list is in Where used.
Critical flows
Each flow has a criticality: Critical, Important or Normal. Set it when you create the flow or in its settings (click the flow's name, or … → Flow settings…).
Critical flows matter in two places:
- The dashboard. Critical flows shows each one passing, failing or not yet run. Next to it, Flows by status counts flows from Draft to Verified, and Recent failed runs lists what broke lately.
- Deployments. The safety check blocks a deployment when a critical flow goes through the system being deployed and the latest run of any of its test cases failed. Test cases that were never run don't block. See CI and the API.
Delete a flow
On the flow, open More and pick Delete flow…, or use Delete flow in its settings. Its test cases and run history go with it, and so do test data and expected results made for its input or output (the dialog names them); its logic stays. You need Edit flows.
In a project that saves edits as drafts, the deletion waits in your changes like any other change: it reaches Trash once they are published to Development. A flow that was never published is only taken out of your changes, with its runs.
Good habits
- Keep each requirement to one testable sentence.
- Link at least one failure test case, not only the normal case.
- Mark a flow critical only if a failure should stop a release.
- Use the requirement's key in the ticket that builds it.
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.
- Change impact and Draft modeSee what an API change would break before anyone feels it, share the drafts for review, and publish them when they are right.
- CI and the APIGate deployments in CI with the safety check and record what you deploy, using an API token and the HTTP API.
