Application-Layer Model Tests
Documentation status: guide — see Maturity and evidence.
Model tests verify executable semantics before UI, transport or deployment concerns obscure failures.
Test order
- Parse and load the package/manifest chain.
- Resolve every
classId, concept and role reference. - Validate constraints and defaults.
- Execute actions with valid and invalid parameters.
- Verify event and process outcomes.
- Round-trip persisted entities where persistence is part of the model.
- Test published contracts through their public adapter only after the model-level behavior passes.
Assertions that matter
Assert conceptual identity, typed references, expected derived state, transaction-visible outcomes and explicit errors. Avoid assertions against private runtime type names, in-memory addresses or physical storage layouts.
CI
Run model validation and contract tests in CI before packaging. If a capability supports both local and remote Runtime adapters, run the same behavioral suite against both.