Skip to content

borghei/Claude-Skills / engineering/qa-browser-automation

qa-browser-automation

Flagged

Live browser QA through Chrome MCP plus Python tools for health scoring, static WCAG checks, screenshot baselines and reports. Use when running a QA sweep on a web app, auditing accessibility, or tracking visual regressions.

assets/qa_report_template.md

View on GitHub
# QA Report: [PROJECT NAME]

**Date:** [YYYY-MM-DD]
**URL:** [Application URL]
**Tester:** [Name or "QA Automation"]
**Tier:** [Quick / Standard / Deep / Exhaustive]
**Branch/Version:** [Git branch or release version]

---

## Executive Summary

[1-3 sentences summarizing overall quality, key risks, and release readiness.]

**Health Score:** [XX]/100 (Grade: [A-F]) — [PASS/FAIL]

---

## Health Score Dashboard

| Category | Weight | Score | Findings |
|----------|--------|-------|----------|
| Console Errors | 12% | --% | -- |
| Broken Links | 8% | --% | -- |
| Visual Consistency | 10% | --% | -- |
| Functional | 18% | --% | -- |
| UX Flow | 12% | --% | -- |
| Performance | 12% | --% | -- |
| Content Quality | 5% | --% | -- |
| Accessibility | 13% | --% | -- |
| Security Headers | 5% | --% | -- |
| Mobile Responsive | 5% | --% | -- |

---

## Findings

### P0 — Critical

[List P0 findings or "None"]

### P1 — High

[List P1 findings or "None"]

### P2 — Medium

[List P2 findings or "None"]

### P3 — Low

[List P3 findings or "None"]

### P4 — Cosmetic

[List P4 findings or "None"]

---

## Accessibility Summary

- **Level Checked:** WCAG 2.1 [A/AA/AAA]
- **Violations:** [count]
- **Compliance:** [XX]%

[Top violations if any]

---

## Performance Summary

| Metric | Value | Status |
|--------|-------|--------|
| LCP | -- | -- |
| INP | -- | -- |
| CLS | -- | -- |
| TTFB | -- | -- |

---

## Visual Regression

- **Pages Compared:** [count]
- **Regressions:** [count]

[List regressions if any]

---

## Recommendations

1. [Priority recommendation]
2. [Secondary recommendation]
3. [Additional recommendation]

---

## Notes

[Additional context, environment details, known limitations, etc.]

---

*Generated by QA Browser Automation skill*
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall