Quality Risk Analysis: Identify, assess, and prioritize the risks that matter
Rank release risks by trigger, impact, evidence and mitigation so test effort targets issues that could change the release decision.
Awesome QA Skills Field Guides
Test Strategy: Clarify scope, risk, and quality gates before testing starts
Plan test scope, levels, environments, data, roles, risks, automation and quality gates around a project's constraints.
Test Strategy Plus: Make scope, risk, and evidence truly traceable
Create a traceable strategy from requirements, architecture, schedule and defect history; keep source versions, conflicts and assumptions visible.
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.
Acceptance Criteria Review: Identify ambiguous, missing, and unverifiable acceptance conditions
Review acceptance criteria for ambiguity, missing states, unverifiable conditions and conflicting rules before implementation or testing begins.
Requirement Gap Analysis: Find rule gaps, exception paths, and undefined states
Compare requirements, interfaces, business rules and historical issues to find missing states, exception paths, conflicting sources and open decisions.
Testability Analysis: Determine whether requirements are truly testable, controllable, and verifiable
Assess testability by checking observable outcomes, controllable conditions, usable data and environments, and safe verification points.
Release Testing Workflow: Complete testing from release preparation to production verification
Coordinate smoke checks, risk regression, defect retests, and residual-risk review before handing a candidate build to release owners.
Requirements Analysis: Find requirement issues before designing tests
Review membership-upgrade requirements for rule conflicts, missing states and untestable wording; capture scope, unknowns and follow-up questions.
Requirements Analysis Plus: Trace requirement sources, differences, and changes across documents
Compare membership-upgrade rules across requirements, prototypes, and APIs; trace conflicts, revisions, open questions, and evidence-backed risks.
Daily Testing Workflow, putting testing into the delivery rhythm
Plan build checks, risk cases, defect retests, and blocker updates, then prepare an evidence-based end-of-day test handoff.
Testing Skill Discovery, putting testing into the delivery rhythm
Map entry points, dependencies, environments, risks, and existing tests in an unfamiliar project, then record gaps and open questions.