Shift-Left QA — Kick-offs, Desk Checks & Website Checklist
本页目录· 10 条
The quality principle
Quality is built across the lifecycle, not inspected in at the end. The Week 9 video uses a V-shaped quality model: defects in the problem statement or design become increasingly expensive because analysis, build and test work must also be changed.
One evidence chain
- Problem statement validation: confirm the user need during design-thinking/ideation.
- Design and prototype review: test whether the proposed interaction solves that need.
- Story kick-off / walkthrough: Product Owner, developer/tech lead and tester clarify acceptance criteria, test approach, data and implementation notes before work starts.
- Pair programming and code review: catch logic, standard and security issues while building.
- Desk check: demonstrate in-development functionality against the user story, persona and acceptance criteria; correct direction before final QA.
- End-to-end and negative testing: test valid paths and intentionally invalid input (for example text where a digit is required).
- Root-cause record: connect each defect to the earlier decision/process that allowed it, then time-stamp the remediation and prevention action.
Async-first version
The article proposes six ways to reduce unnecessary meetings while preserving feedback:
- agree overlap time and response expectations;
- align Definition of Ready and Definition of Done;
- have the “three amigos” detail the story;
- queue ready stories so questions can be raised early;
- use checklist-guided recorded demos for suitable desk checks;
- still meet synchronously when ambiguity or risk warrants it.
Measure the effect: waiting time, reopened work, defects found late and time from ready → done.
Website QA coverage
UI & content
- visual consistency, spacing, states, images and responsive layout;
- spelling, headings, navigation, metadata, placeholders, 404 and duplicate content.
Functionality
- link destinations, buttons, fields, tables, search, tabs and forms;
- valid, invalid and boundary input;
- confirmation, failure and recovery paths;
- media, cookies and disconnected/expired-session behaviour.
Accessibility
- alt text, labels, captions, keyboard/logical structure, zoom and sufficient contrast.
Compatibility, performance and security
- device, browser and operating-system coverage;
- readable/responsive navigation and forms;
- privacy, authentication/error behaviour, secure transport and logging;
- external scripts, widgets and analytics.
Evidence artefacts
- QA checklist with owner, environment and result.
- Defect log with severity, reproduction steps, evidence and status.
- Story/acceptance criteria linked from each relevant test.
- Screenshot or recording for desk check and critical paths.
- Root-cause and prevention action for material defects.
- Governance-folder link and ePortfolio evidence.