propagate

To generate tests from Allium specs automatically, provide the spec plan, domain model, and target codebase. The skill outputs test scaffolds reflecting specified obligations, plan outputs, and state machine definitions aligned with project conventions.

Automating state machine testing from specifications involves converting model definitions into concrete test scaffolds. This approach systematically generates tests for state graphs, transitions, invariants, and edge cases to ensure full spec coverage.

Yes, you need both a domain model and a spec plan to generate property-based tests. Systematic test generation requires access to these inputs alongside the target codebase to accurately map obligations and produce valid test scaffolds.

Yes, you can generate cross-module test scaffolds for inter-component interactions. The process produces skeleton tests for surfaces and component interactions, ready for direct wiring into your existing test suites and project conventions.

Generating tests from spec obligations requires access to the spec plan, domain model, and target codebase. It outputs test scaffolds following project conventions, meaning the generated files are skeleton tests requiring wiring into existing test suites.

Spec-to-tests mapping handles obligations by converting plan outputs and model definitions into concrete test scaffolds. It ensures full coverage of a given spec by systematically mapping the specified obligations directly into aligned test files.