Skip to content

Testing Strategy

Mandatory standards

  • Changes should be validated before release
  • Tests should cover the behavior that matters most for correctness and regressions
  • Test failures should be actionable
  • The test strategy should match the risk of the change
  • Use unit tests for fast feedback on logic-heavy code
  • Use integration tests when boundaries matter
  • Use end-to-end or system tests where user or release flows need confidence
  • Keep tests deterministic and isolated where practical

CI/CD alignment

CI/CD should run the most valuable tests automatically so that validation happens close to the change.

Build reproducibility

Testing should not rely on hidden local state. If a test requires setup, that setup should be documented and reproducible.