Testing Strategy
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
A global testing strategy starts from model validity and continues through runtime, service and published-contract verification.
Semantic tests verify model rules, identities, constraints and action outcomes, not only HTTP responses or implementation methods. The source recommends tests across declaration validation, model assembly, runtime invocation and published contract boundaries. A validated example is stronger evidence than an illustrative snippet.
Engineering rules
- Write positive, negative and boundary cases for domain invariants.
- Separate model test failures from runtime, transport and adapter failures.
- Run the same contract against each supported execution surface.
- Record the source, release and environment for a verified example.
Chapter outline (original LaTeX headings)
- Purpose
- What to Test
- Structure a Declarative Test Package
- Declare a Test Suite as a Model
- One Test Case per Declared Action
- Assertions in functionalP
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/testing-conceptual-models.tex.