qa-and-browser-verification

name	qa-and-browser-verification
description	Use when the task involves QA planning, manual workflow verification, browser testing, UI regression review, issue taxonomy, QA health scoring, screenshot/video evidence, adverse-state testing, fix loops, and APIVR Phase 5 verification for frontend, workflow, or user-visible changes.
activation	Activate when the description trigger applies to the current task.
required_inputs	Task request, relevant repository context, constraints, and authority dependencies.
required_outputs	Skill-specific artifact, verification evidence, canonical verdict, and next action.
authority_dependencies	00_start_here/SOURCE_OF_TRUTH.md; 10_governance/APIVR_EXECUTION_LIFECYCLE.md; 10_governance/source_of_truth/Elite_Build_Goals_v3.md.
evidence_requirements	Executed checks or an honest Unknown, Not Run, or Blocked state for every material claim.

QA And Browser Verification

Use this skill when success depends on a user-visible workflow, rendered interface, browser behavior, or manual acceptance path.

Browser QA alone cannot PASS workflows that depend on outside providers calling the app. For webhooks, OAuth/Auth callbacks, cron routes, payment/email/SMS providers, deployment protection, or Preview/Production environment splits, also use `skills/external-integration-launch-gate/SKILL.md`.

QA Flow

flowchart TD
  A["Define user workflow"] --> B["Create QA matrix"]
  B --> C["Run happy path"]
  C --> D["Run adverse states"]
  D --> E["Run responsive/accessibility checks"]
  E --> F{"Issue found?"}
  F -- "Yes" --> G["Classify, fix narrowly, retest affected path"]
  G --> C
  F -- "No" --> H["Record QA health report and APIVR verdict"]

Required QA Matrix

• Happy path.
• Empty state.
• Loading state.
• Error state.
• Permission or auth boundary.
• External provider callback boundary when applicable.
• Responsive viewport checks.
• Accessibility checks.
• Data accuracy checks when reporting or analytics are visible.

Issue Taxonomy

• Blocker: prevents core workflow or creates safety/security/data risk.
• Major: harms important workflow, trust, accessibility, or release readiness.
• Minor: visible polish issue with low functional risk.
• Observation: not a bug, but useful product or quality note.

Worked Example

Scenario: A new admin report page.

• QA runs desktop and mobile viewports, empty dataset, provider timeout, export action, and keyboard navigation.
• Finding: mobile table overflows and export button is hidden.
• APIVR state: UI release gate is Blocked until fixed and retested.
• Final verdict: PASS only when screenshot evidence, export evidence, and adverse-state checks are recorded.

Scenario: A premium upgrade flow returns from Stripe.

• Browser QA verifies the user-visible checkout return and premium card state.
• External integration launch gate verifies Stripe webhook delivery into the deployed URL, no login redirect, correct signature handling, database update, provider event ID, and app log.
• Final verdict: PASS only when both the browser result and provider callback path are Verified.