Development, testing and delivery
Toolora development uses local dependencies and a disposable Supabase stack for automated fixtures. GitHub pull requests provide code review and selected CI checks. Exact-commit release tooling publishes application and schema candidates under separate safeguards. Delivery status distinguishes these steps from a verified business outcome.
Local development and synthetic data
Section titled “Local development and synthetic data”The development guide owns dependency installation and local startup commands. The local stack is built from the repository’s migrations, and synthetic data supports isolated testing. Reset and seed tools derive their database from local Supabase status. Shared runtime configuration is not an input for automated reset tools.
Prepare an isolated development environment provides the detailed contract, examples and verification limits.
Test levels and evidence
Section titled “Test levels and evidence”Unit, component, hermetic backend and local database suites cover different behaviours. Authenticated browser and delivered-mail checks have separate execution contracts. The CI selector chooses surfaces for a candidate and defers application suites on draft PRs. Evidence interpretation must name the scenario, version, target and actual result of a check.
Test levels and selected checks provides the detailed contract, examples and verification limits.
Pull requests and application release
Section titled “Pull requests and application release”A coherent issue batch uses an integration branch and draft PR. Relevant local checks precede readiness. Publication builds an exact commit and verifies the affected running component and business flow. Application-only candidates can be published during pre-launch under the release contract. Runtime publication remains distinct from merging to main.
Review and publish a coherent change provides the detailed contract, examples and verification limits.
Schema delivery and compatibility
Section titled “Schema delivery and compatibility”Schema delivery requires forward migrations, a fresh backup, source and catalogue checks and the guarded release path. Compatibility may require stopping old writers before the new application runs. Application rollback retains the schema. Migration rules and recovery procedures define the appropriate forward correction or restoration boundary.
Publish compatible database changes provides the detailed contract, examples and verification limits.