Test Strategy Review: Review scope, risk, and release gates based on evidence
Review test risks, resources, environments, and exit criteria; turn vague feedback into evidence-linked findings with impacts and checkable revisions.
Quality Analyst, Not Quality Assurance.
Review test risks, resources, environments, and exit criteria; turn vague feedback into evidence-linked findings with impacts and checkable revisions.
Review acceptance criteria for ambiguity, missing states, unverifiable conditions and conflicting rules before implementation or testing begins.
Compare requirements, interfaces, business rules and historical issues to find missing states, exception paths, conflicting sources and open decisions.
Assess testability by checking observable outcomes, controllable conditions, usable data and environments, and safe verification points.
Coordinate smoke checks, risk regression, defect retests, and residual-risk review before handing a candidate build to release owners.
Review membership-upgrade requirements for rule conflicts, missing states and untestable wording; capture scope, unknowns and follow-up questions.
Compare membership-upgrade rules across requirements, prototypes, and APIs; trace conflicts, revisions, open questions, and evidence-backed risks.
Plan build checks, risk cases, defect retests, and blocker updates, then prepare an evidence-based end-of-day test handoff.
Map entry points, dependencies, environments, risks, and existing tests in an unfamiliar project, then record gaps and open questions.
Place requirement review, test design, execution, defect work, and retrospectives into a sprint plan with clear inputs and evidence.