Testing and model evolution

Documentation status: tutorial — see Maturity and evidence.

Test the application as an executable conceptual model, not only as implementation code.

Minimum test layers

1. Loading - package, manifest and all five core concepts resolve.
2. Model validity - required roles, score ranges and relation constraints are enforced.
3. Actions - SubmitRequest, ComputeRisk, review and finalization actions return the expected state/results.
4. Events/process - significant transitions emit the expected events and the process can resume after asynchronous work.
5. Views - DataSources and DataSets resolve, master/detail context follows the current request and before-post validation can cancel invalid input.
6. Publication - published actions enforce request shape, authorization and process state.
7. .NET - generated client code sees the same capabilities in local and RPC modes.
8. AI - assistant proposals cannot bypass published actions or human-validation requirements.

Evolution tests

When adding an indicator, rule or review step, regression-test role paths, persistence projections, public action signatures, event names and generated binding shape. These are common compatibility boundaries.

Keep small representative XML/YAML fixtures when both forms are supported. Compare runtime-significant meaning, not textual formatting.