Skip to content

Quality Gates

Status: 🌱

Motivation

Define objective merge and release criteria across frontend and backend to reduce regressions and improve delivery confidence.

Starter Points

  • Shift fast checks left: run strict typing, lint rules, and lightweight validation before push to shorten feedback loops.
  • Prefer editor/IDE-integrated checks aligned with project standards and use optional git hooks for checks that finish in a few seconds.
  • Keep PR validation focused on architecture and high-level quality signals: design boundaries, behavior risk, contracts, and operational impact.
  • Avoid PR churn on low-value style checks that are better enforced automatically before push.
  • Require behavior-based tests for critical UI and API-driven user flows; keep snapshots as secondary checks.
  • Require backend unit tests for domain rules and edge cases.
  • Define integration boundaries: test real adapters (database, queue, HTTP client contracts) without coupling everything into full end-to-end.
  • Use stubs for deterministic collaborator behavior and mocks for interaction assertions where side effects matter.
  • Set suite speed budgets, isolate slow tests, and keep flaky-test ownership explicit.
  • Enforce CI quality gates: test pass, artifact traceability, and container image validation (vulnerability scan and provenance).
  • Run smoke checks after deploy and keep rollback paths documented.