Generate Unit-Test Scaffolding

Documentation status: guide — see Maturity and evidence.

The editor tooling can help generate test scaffolding from the current application/model context. Generated tests are a starting point, not proof of behavior.

Recommended workflow

1. Build/validate the model first.
2. Select the concept, action, process or service contract to test.
3. Generate the test skeleton.
4. Replace placeholder data with explicit fixtures and expected outcomes.
5. Add negative and boundary cases.
6. Run the tests against the supported Runtime mode.
7. For binding contracts, repeat against local and remote adapters where the capability is supported.

What to test

Prefer contract-level assertions: identity, type resolution, relation roles, action parameters/results, persistence round trips, event/process outcomes and explicit failure semantics. Avoid tests that assert private implementation-class names or storage layouts.