Must Know: Definition of Done

Prerequisites

• - Agreed quality gates across engineering, UX, and QA.
• - Automated checks in CI for build and tests.
• - Manual validation checklist for responsive and accessibility behavior.

Step 1: Pass automated quality gates

Build and test must pass before review is complete.

npm test
npm run build:storefront

Step 2: Pass accessibility and interaction checks

Validate keyboard operability, visible focus, reduced-motion behavior, and contrast.

Checklist:
- Visible keyboard focus on all controls
- Logical tab order
- Reduced motion respected
- WCAG AA contrast

Step 3: Pass responsive and docs integrity checks

Verify no horizontal overflow and valid navigation at standard viewport widths.

Viewport validation:
- 375
- 768
- 1024
- 1440

Release Checklist

• - No broken routes or dead links in intro and section pages.
• - No silent runtime errors for core interactions.
• - Docs updates reflect shipped behavior and support paths.
• - News pages include release communication needed for adopters.

Troubleshooting

• - If a gate repeatedly fails, document the failure mode and add a regression test.
• - If manual checks are skipped, convert recurring checks into automated scripts where possible.
• - If definition-of-done items conflict, align ownership and merge criteria before sprint close.

Next Actions