Testing and command reference

Testing and command list

The shared recipe selects checks through herd/project.json; inspect both for the actual scope. Database integration tests require a disposable database in GOAT_TEST_DSN; without it they may skip. GOAT_TEST_LEGACY_SCHEMA supplies an old schema snapshot for upgrade tests. Generated browser tests and child smoke checks are separate. Historical results in child/e2e/VALIDATION.md describe their recorded run only. Use goat help <command> for Goat options and <command> --help for application commands. CLI releases are documented in child/goatcli/RELEASING.md.

goat run:script --path=@goatcms/herd/test.goat
goat run:script --path=@goatcms/herd/e2e.goat
goat run:script --path=@goatcms/herd/test/contracts.goat

• Getting Started with Goat
• Environment configuration
• Project Architecture
• Local Development
• Database and migrations
• Test data and fixtures
• Data model and code generation
• New project: from goat init to your first model
• Board automation