Logic Assurance
Overview
Logic Assurance is the testing agent for Flowon on Microsoft Dataverse. It reads a project's executable logic, process flows, decision tables and trees, validations and validation sets, and formulas, and generates ready-to-run test suites for it. A fleet of specialist generators reads each artifact, pulls in the Dataverse entity metadata it touches, and produces structured test cases with concrete inputs and precise expected outcomes, then stores them per artifact.
It answers the question every team asks before they change something: if I touch this, what should still hold true. Instead of writing that answer by hand, one test case at a time, Logic Assurance produces a grounded starting suite for every piece of logic in the project.
Logic Assurance runs as a self-contained container with its own web application, connects through the Flowon MCP server, and is strictly read-only against your project. It reads your logic and writes test suites to its own store; it never changes the project.
The problem it solves
Logic built without code still needs testing, and it rarely gets it. Validations, formulas, decision tables, and flows encode real business rules, and when someone edits one, there is usually nothing that catches the regression. Writing tests by hand is slow and needs someone who knows both the rule and the exact shape of the data, so it does not happen. The logic ships untested, and the first sign that a change broke something is a wrong result in production.
Logic Assurance removes the two barriers that stop teams from testing low-code logic: the effort of writing cases, and the knowledge of the data model needed to write them well. It generates the cases, and it grounds them in your real Dataverse schema, so the suite is meaningful from the first run.
What it produces
| Deliverable | What you get |
|---|---|
| Test suites per artifact | A set of named test cases for each piece of executable logic |
| Schema-accurate cases | Inputs and expected saves that use your real Dataverse field names and types |
| Typed expectations | Boolean results, expected outputs, expected entity saves, and expected calls |
| Coverage tracking | A per-artifact count of how many test cases exist, so you can target the gaps |
| Editable, persisted suites | Suites you can review, refine, and keep as the source of truth |
Who it is for
- Makers who want a safety net for the logic they build, without writing tests by hand.
- QA and test engineers who need a grounded starting suite instead of a blank page.
- Platform teams who want a baseline of coverage across every project.
- Anyone about to change existing logic who needs to know what the correct behavior is supposed to be.
How it fits the platform
Logic Assurance tests the executable logic you build with Logic Composer, reading both the logic and the live Dataverse schema through Flowon Logic Assist (the MCP server). It is the regression safety net for the rules that run your business.
Explore Logic Assurance
| Page | Contents |
|---|---|
| How It Works | The generator fleet, metadata grounding, and the generation pipeline |
| Test Cases & Coverage | The test-case model, expectations, coverage, and editing |
| Configuration & API | Per-project settings and the REST surface |
Ready to run it? See the Installation guide.