pwdev-qa

Use when a user asks for QA planning, execution, review, release assessment, reporting, status, or test-tool recommendations and the correct PWDEV QA workflow must be selected safely.

Record a reproducible defect, independent triage, immutable attempts, and evidence-backed retest state.

Execute an explicitly authorized exploratory charter and record notes, findings, evidence, and follow-up without claiming false coverage.

Initialize or inspect project-local PWDEV QA context without overwriting existing state or installing tools.

Build an impact-based regression selection with explicit traceability, inclusions, exclusions, and limitations.

Produce an evidence-backed release readiness opinion while keeping the human release decision separate.

Export one validated QA manifest as matching HTML and PDF without executing tests or evidence commands.

Review requirements, coverage, results, evidence, and findings without changing the product or recorded state.

Design traceable accessibility checks that combine scanners with observable keyboard, focus, semantic, and assistive-technology behavior.

Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.

Design isolated repeatable automation, distinguish interactive browser exploration, and handle flaky results through evidence and reproduction.

Design deterministic CI quality gates that read the normalized manifest verdict independently from report-export process status.

Design traceable data checks for reconciliation, integrity, transactions, and atomicity with separate observable oracles.

Triage defects with independent severity and priority, reproducible evidence, preserved attempt history, and explicit resolution retesting.

Design traceable functional test conditions across positive, negative, boundary, and error behavior with observable expectations.

Define auditable QA metrics with explicit numerators, denominators, populations, windows, and treatment of every result state.

Design platform-specific Android and iOS checks with explicit SDK, driver, device, lifecycle, and evidence prerequisites.

Design bounded performance profiles with explicit load authorization, contextual samples, percentiles, and agreed thresholds.

Plan explicitly authorized read-only production observations and trace evidence-backed causes into preventive regression coverage without external effects.

Assess release readiness from applicable criteria, all current defects, risks, limitations, and recorded human decisions without approving release.

Select traceable regression coverage from change impact, affected risks, criteria, dependencies, and prior defects rather than execution convenience.

Assess requirement clarity, testability, completeness, consistency, and traceability without inventing missing acceptance criteria.

Design authorized, bounded, reproducible security checks without turning scanner findings into penetration-test permission.

Analyze product risk and propose traceable QA coverage, priorities, environments, data, and explicit coverage gaps.

Design traceable Web and browser checks with explicit browser coverage, observed interactions, isolated sessions, and evidence limitations.

Summarize existing QA criteria, cases, evidence, defects, limitations, authorization, and verdict without mutation.

Produce a traceable risk-based QA strategy without executing tests or expanding authorization.

Execute explicitly authorized tests and record traceable expected, observed, evidence-bound results.

Recommend context-appropriate QA tools while preserving observed availability, constraints, and safer alternatives.