SmokeRegression
Smoke tests (minimal 'is it alive' checks post-deploy) and regression tests (confirming old bugs stay fixed) — network engineering calls the post-deploy check 'PIV' (Post-Implementation Verification); same concept, see DeveloperTools/DeploymentStrategies/PostImplementationVerification-PIV for the rollback-on-failure angle.
Why we need this / what value this brings
A fast 'is it even alive' check catches catastrophic deploy failures immediately, before deeper (slower) testing even runs.
When to use this
Immediately after every deploy, and any time a previously-fixed bug is a plausible risk again.
How to use or implement this
Keep smoke tests minimal and fast (can the app boot and respond to a health check); run the full regression suite separately.
Research questions
- Is there a smoke test that runs immediately after
docker compose upto confirm the stack actually boots clean?
Empty folder — drop notes, links, and findings here as you research.