Automation Testing: Decide what to automate before choosing tools and frameworks
Choose stable, frequent regression paths for automation, weigh maintenance and environment costs, and define a CI-ready rollout.
Awesome QA Skills Field Guides
Test Report Review: Check whether conclusions, evidence, and release impact align
Audit test report metrics, evidence links, failure handling, residual risk and whether its recommendations exceed available proof.
Playwright UI Automation Testing: Build reliable regression with stable locators and controlled data
Stabilize Playwright regression checks with observable states, durable locators, and isolated test data so failures identify broken user-facing behavior.
Bug Reporting: Turn “it sometimes fails” into a defect developers can reproduce reliably
Turn intermittent failures into reproducible defects by recording time, account state, request trail, result, and user impact.
Test Data Generation: Systematically cover normal, boundary, exceptional, and permission scenarios
Create reproducible data for low balances, tenant boundaries, expired coupons, and date edges without carrying sensitive production data into tests.
Test Reporting: Turn test results into actionable quality conclusions
Turn test results into release evidence with coverage, failure impact, residual risk and a clear recommendation for risk owners.
Test Case Review: Find coverage gaps, ambiguous assertions, and high-risk scenarios
Review cases for coverage gaps, duplicates, impossible preconditions and vague assertions, with each finding tied to an affected risk and fix.
Test Case Review Plus: Trace high-risk gaps across requirements, cases, and evidence
Compare test cases with requirements, risk registers and source material to expose conflicts and high-risk gaps with traceable evidence.
Test Case Writing Plus: Keep requirements, rules, and test cases traceable end to end
Track requirements, API rules, and risk sources before writing cases; resolve version conflicts and keep every case traceable.
Accessibility Testing: Systematically validate the full user experience from keyboard operation onward
Review checkout access across keyboard, focus, labels, errors, and screen-reader output; tie findings to controls and user impact beyond automated scans.
Mobile Testing: Cover weak networks, permissions, and app lifecycle scenarios
Test mobile behavior across weak-network recovery, permission changes, interruptions, and app restarts to expose state and request failures.
Test Case Writing: Turn acceptance criteria into executable, verifiable test cases
Convert order acceptance criteria into test cases with data, steps, and observable outcomes; retain traceability and flag gaps instead of inventing rules.