Manual Smoke Tests

Last reviewed: 2026-05-13
Maintained by: Engineering

Use this page as the lightweight manual verification checklist after changes that affect runtime behavior.

Core smoke path

1. Start the API and the app you changed.
2. Confirm the main authenticated shell loads.
3. Confirm the changed flow completes without console or server errors.
4. Confirm related list/detail views still render with seeded data.
5. Confirm no new env variables or startup steps are undocumented.

App-focused smoke prompts

• API: health endpoint responds and the changed route returns the expected envelope
• Manager Desk: sign-in, navigation, and changed feature flow work against local API
• Back Office: sign-in and target admin flow work against local API
• Mobile: app boots, auth restores correctly, and target screen flow reaches the API

Documentation rule

If a feature needs a repeatable smoke checklist beyond this baseline, add it beside the owning runbook or expand this page with a dedicated section.