common-web-visual-testing
/common-web-visual-testing
Standardizes visual audits, responsive design, and behavioral testing for web apps. Use to verify a web UI fix or cross-browser behavior; defer backend API refactors, Playwright installation/tooling setup, and Appium/mobile automation.
- Author
- HoangNguyen0403 ↗
- Repository
- agent-skills-standard ↗
- Licence
- MIT
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 6
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Standardizes visual audits, responsive design, and behavioral testing for web apps. Use to verify a web UI fix or cross-browser behavior; defer backend API refactors, Playwright installation/tooling setup, and Appium/mobile automation.
Original author description
Standardizes visual audits, responsive design, and behavioral testing for web apps. Use to verify a web UI fix or cross-browser behavior; defer backend API refactors, Playwright installation/tooling setup, and Appium/mobile automation.
How it works
- Priority: P1 (HIGH)
- 🧪 Testing Mindset (Comparative Audit)
- 📋 Scenario Matrix
- 🚫 Anti-Patterns
- 📁 Evidence
- 🔗 References
SKILL.md preview
---
name: common-web-visual-testing
description: Standardizes visual audits, responsive design, and behavioral testing for web apps. Use to verify a web UI fix or cross-browser behavior; defer backend API refactors, Playwright installation/tooling setup, and Appium/mobile automation.
metadata:
triggers:
keywords:
- web test
- browser test
- responsive audit
- verify web ui
- cross-browser check
- web accessibility
---
# 🌐 Web Visual & Behavioral Testing
## **Priority: P1 (HIGH)**
> [!IMPORTANT]
> **Tier 2 (Methodology)**: Strategy web UI/UX audit.
> **Tier 3 (Domain)**: Responsive, A11y (WCAG), Browser Engine quirk.
## 🧪 Testing Mindset (Comparative Audit)
Visual test best as **Comparative Audit** loop:
1. **Baseline (Before)**: Capture `snapshot --aria` + `screenshot` prod/main.
2. **Implementation (After)**: Capture same local/feature.
3. **Audit**: Compare state for regression, CLS, Aria drift.
Responses must label the two captures as **Before** and **After** (or Baseline and Fixed) and include the diff and neighboring-element side-effect check.
## 📋 Scenario Matrix
| Change Type | Scenarios to Run |
| :---------------- | :------------------------------------------------- |
| **CSS/Layout** | Responsive Audit + Hover + CLS Check |
| **Forms/Input** | Validation Msg + Focus State + Error Boundary |
| **Navigation** | URL Sync + Sticky Header + Back-Button Persistence |
| **Assets/Fonts** | Lazy Load + Icon Check + LCP Audit |
| **Accessibility** | Tab Order + Aria-Snapshot + Color Contrast |
## 🚫 Anti-Patterns
- **Single-Viewport**: Never verify Desktop only. Check Mobile (375px) + Tablet (768px).
- **Ignore Layout Shift**: Check loading state (skeleton) → no page jump.
- **Unmasked Dynamic**: **MUST** mask timestamp/balance via `--mask` or JS (`opacity: 0`). Avoid "False Regression".
- **Blind Assertion**: Use `playwright-cli snapshot --aria` (CLI) or `browser_snapshot` (Playwright MCP) verify state before done.
## 📁 Evidence
Before/After pairs live in `.playwright-cli/<session>/` as `<AC|step>-before.png` / `<AC|step>-after.png` plus matching `.aria.txt`. Driver rung and dir go in the walkthrough `driver:` / `evidence_dir:` lines.
- **External Dependency**: Mock/bypass 3rd-party (Chat, Analytics) → prevent flakiness.
## 🔗 References
- **playwright-cli**: [playwright-cli](../../quality-engineering/quality-engineering-playwright-cli/SKILL.md)
- **Driver Ladder**: [driver-ladder](../../quality-engineering/quality-engineering-playwright-cli/references/driver-ladder.md) — CLI first, Playwright MCP fallback, BLOCKED rule.
- **Diagnostic Decoder**: [diagnostic-decoder](references/diagnostic-decoder.md)
- **DOM vs Screenshot**: [dom-snapshot-vs-screenshot](references/dom-snapshot-vs-screenshot.md)
- **Login & Data**: [login-and-test-data](references/login-and-test-data.md)
- **Scenario Details**: [scenarios](references/scenarios.md)
Files in this package (6)
- LICENSE 1 KB
- SKILL.md 3 KB
- references/diagnostic-decoder.md 5 KB
- references/dom-snapshot-vs-screenshot.md 3 KB
- references/login-and-test-data.md 4 KB
- references/scenarios.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · HoangNguyen0403/agent-skills-standard | 100 | MIT |
| HoangNguyen0403/agent-skills-standard | 100 | MIT |
Identical content appears in 4 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 5bdc6d23591d (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100e2e-tester
/e2e - Senior QA Automation Engineer with 10+ years E2E testing experience. Use when writing end-to-end tests for web apps with Playwright, mobile apps with Detox, testing critical user flows, cross-browser testing, visual regression testing, or performance testing. Also… - 100playwright-automation
Browser automation and testing with Playwright. Use when testing web applications, automating browser tasks, taking screenshots, or validating UI behavior. - 90vc:web-testing
Web testing with Playwright, Vitest, k6. E2E/unit/integration/load/security/visual/a11y testing. Use for test automation, flakiness, Core Web Vitals, mobile gestures, cross-browser. - 100visual-qa
Use when verifying that a UI renders correctly. Covers visual regression testing, responsive checks across breakpoints, cross-browser verification, and screenshot-based review of an implementation against a design. Trigger on "does this match the figma", "set up screenshot… - 100playwright-testing
Playwright E2E testing — cross-browser, visual regression, API testing, mobile emulation. Use when writing E2E tests or setting up automated UI testing for web apps. - 100e2e-playwright-testing
End-to-end testing with Playwright for web applications. Use when writing E2E tests, browser automation, form submission testing, or user flow testing. Triggers on "playwright", "e2e test", "browser test", "end-to-end", "form flow testing", or test files in tests/e2e/.