QA Browser Automation

QA Browser Automation

The agent drives Chrome MCP for live browser testing and uses four Python tools for deterministic health scoring, accessibility auditing, visual regression tracking, and report generation.

Clarify First

Before the QA sweep, confirm these inputs. If any is unknown or vague, ASK — do not assume:

• Target URL/app + auth — what to test and how to log in (the subject of the entire sweep)
• Testing tier — Quick / Standard / Deep / Exhaustive (sets scope, breakpoints, and duration)
• Fix autonomy — auto-fix P3/P4 and commit, vs report-only / ask before any code change (changes whether the working tree is modified)
• WCAG target level — A / AA / AAA (sets the accessibility pass bar)

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.

Quick Start

# Score QA findings (0-100 weighted across 10 categories)
python scripts/qa_health_scorer.py findings.json --threshold 85 --baseline .qa-baselines/latest.json --save-baseline --json

# Audit HTML for WCAG 2.1 violations
python scripts/accessibility_auditor.py page.html --level AA --json

# Track visual regressions
python scripts/visual_regression_tracker.py --init --baseline-dir ./baselines
python scripts/visual_regression_tracker.py --register ./baselines
python scripts/visual_regression_tracker.py --baseline ./baselines --current ./screenshots --threshold 5

# Generate full QA report
python scripts/test_report_generator.py session_data.json --format markdown -o report.md

Tools Overview

All tools support --json for machine output. Health scorer and regression tracker return exit code 1 on failure (CI-friendly).

Workflow 1: Full Application QA Sweep (11 Phases)

Phase 1-2: Pre-flight and authentication.

• Verify git status is clean. Abort if dirty.
• Create session directory: .qa-sessions/{timestamp}/
• Authenticate via Chrome MCP if needed.

Phase 3-4: Orient and explore.

• Use mcp__claude-in-chrome__read_page to build sitemap/page map.
• Navigate each route. Check read_console_messages for errors, read_network_requests for 4xx/5xx.
• Test all forms with valid data, empty submissions, and boundary values.

Phase 5: State testing.

• Verify loading states (skeleton screens, not blank), empty states (guides to first action), error states, success states, partial states.
• Four shadow paths per interaction: happy path, nil input, empty input, error upstream.

Phase 6: Cross-device and security.

• Resize to 320px, 768px, 1024px, 1440px, 1920px.
• Check touch targets (44x44px min), layout shifts.
• Verify security headers (CSP, HSTS, X-Frame-Options), cookie flags.

Phase 7-8: Document and score.

• Record every finding with screenshot evidence. No finding without evidence.
• Classify by severity (P0-P4) and category (10 categories).
• Run: python scripts/qa_health_scorer.py findings.json --baseline .qa-baselines/latest.json

Phase 9: Triage and fix loop.

• P3/P4: AUTO-FIX, commit atomically, verify.
• P0/P1/P2: ASK, present evidence, propose fix, wait for approval.
• After each fix: re-run check. If fail: git revert.
• Hard stop at 50 fixes.

Phase 10-11: Regression check and report.

• Re-visit fixed pages. Verify no new errors.
• Generate report: python scripts/test_report_generator.py session.json --save-baseline

Validation checkpoint: Health score >= 85. Zero P0 findings. WCAG AA >= 95%.

Workflow 2: Visual Regression Testing

# Set up baseline
python scripts/visual_regression_tracker.py --init --baseline-dir ./baselines
# Capture and register screenshots
python scripts/visual_regression_tracker.py --register ./baselines
# After changes, compare
python scripts/visual_regression_tracker.py --baseline ./baselines --current ./screenshots --threshold 5 --json
# Accept intentional changes
python scripts/visual_regression_tracker.py --update-baseline --baseline ./baselines --current ./screenshots

Pages exceeding the threshold (default 5%) are flagged as regressions. Uses SHA-256 hashing and byte-level comparison.

Workflow 3: Accessibility Audit

python scripts/accessibility_auditor.py page.html --level AA --json
curl -s https://example.com | python scripts/accessibility_auditor.py - --level AAA

What gets checked by level:

• A (Must Fix): Alt text, page language, form labels, headings, duplicate IDs, autoplay media
• AA (Should Fix): Color contrast (4.5:1 text, 3:1 large), heading hierarchy, focus visible, error identification
• AAA (Nice to Have): Enhanced contrast (7:1), extended audio, reading level

Each violation includes: WCAG criterion, severity, element selector, and remediation guidance.

Testing Tiers

Health Scoring System

10 weighted categories, score 0-100:

Severity deductions: P0: -30, P1: -18, P2: -10, P3: -4, P4: -1.

Grades: A (90-100), B (80-89), C (70-79), D (60-69), F (0-59).

Safety Controls

• Clean working tree required -- abort if git status dirty.
• Max 50 fixes per session -- hard stop.
• Risk accumulator -- component (+5), style (+2), config (+8), revert (+15). Stop at 25% of budget.
• WTF heuristic -- 3 consecutive fix verification failures = stop entirely.
• Atomic commits -- one fix = one commit: fix(qa): [P{severity}] {description}

Troubleshooting

References

Integration Points

Last Updated: April 2026 Version: 2.1.0