What Users Should Care About
- Critical workflows are protected by automated release checks before changes ship.
- Authentication, permissions, and workspace isolation are continuously validated.
- Performance guardrails catch latency and error-rate regressions on key paths.
- User-facing flows are regression-tested to reduce breakage in day-to-day operations.
Release and Reliability Policy
- Blocking quality gates run on pull requests and protected-branch updates.
- External documentation checks run in non-blocking mode with triage reporting.
- Risky changes require targeted regression suites before release approval.
- Failures are handled with rollback-first incident response and runbook-guided remediation.
Operational Confidence Signals
- Authentication and invite/member flows stay guarded by API and UI regression coverage.
- Dashboard and module navigation remain protected by end-to-end checks.
- Security and docs quality workflows produce artifacts for auditability and follow-up.
- Reliability posture is validated continuously, not only right before release.
For Developers
Need technical testing detail (unit/API/e2e/perf commands, CI gate definitions, and docs-link automation contracts)? Use these references:
docs/testing.md(full engineering test matrix and commands)- API v1 (API contracts and versioning)
- Architecture (system flow and boundaries)
- Operations and Runbooks (incident procedures)