Testing & Quality¶
This section groups the project's testing strategy, automated checks, coverage, performance evidence,
formal user testing and defect workflow. The detailed evidence itself remains under evidence/ and is
linked through Project Process & Evidence.
What do you need to verify?¶
| Question | Start here |
|---|---|
| What test suites exist and how do I run them? | Automated testing strategy |
| What does CI require before merge/deployment? | CI/CD & quality gates |
| How is repository-wide coverage calculated? | Code coverage |
| How is performance measured? | Representative-scale performance baseline |
| How is formal user testing run? | User testing overview |
| What rules govern a user-testing session? | User testing protocol |
| What tasks can participants be given? | User testing task bank |
| What did formal user testing find? | Sprint 2 summary and Sprint 3 summary |
| What proves Intermediate ingestion works end to end? | Intermediate ingestion acceptance |
| How are defects reported and tracked? | Bug tracking |
| Where are retained validation records? | Testing & validation evidence |
Fast local checks¶
The root package scripts remain authoritative. Common entry points are:
npm run hygiene
npm run check
npm run test
npm run test:coverage
Database, browser, deployment and feature-specific commands are documented in the automated testing strategy rather than repeated here.
User testing vs automated testing¶
Automated checks establish repeatable technical behaviour. Formal user testing evaluates whether representative users can understand and complete product journeys. They are complementary evidence streams and should not be collapsed into one result.
Use User Testing Overview for the process and Testing & Validation Evidence for retained evidence and traceability.
Performance and deployment acceptance¶
Local response-time measurements belong in the performance baseline. Hosted capacity, recovery and production-scale deployment acceptance belong under Deployment & Operations and its linked acceptance/recovery pages.
AI Declaration¶
The testing/quality documentation hub and evidence separation were planned and drafted with the assistance of ChatGPT-Web[GPT-5.6 Sol].