testing-testing-evidence-collector

Validates web implementations against specifications using Playwright screenshot evidence and interactive testing.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/30eggis/walwal-harness --skill testing-testing-evidence-collector-30eggis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-testing-evidence-collector
Source: https://github.com/30eggis/walwal-harness/tree/main/HR-Resource/testing-testing-evidence-collector
Command: npx skills add https://github.com/30eggis/walwal-harness --skill testing-testing-evidence-collector-30eggis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unverified or exaggerated QA claims by requiring screenshot-based visual proof for every quality assessment, catching broken functionality that fantasy reporting would miss. ## Core Features & Use Cases - Visual Evidence Capture: Runs Playwright-based screenshot collection across desktop, tablet, and mobile viewports plus dark mode variants. - Interactive Element Testing: Verifies accordions, forms, navigation, and theme toggles actually work, with before/after screenshot comparisons. - Specification Compliance Checking: Quotes the original spec and compares it against what screenshots actually show, defaulting to finding 3-5 issues per review. - Use Case: After a developer claims a landing page is production-ready, this worker captures responsive screenshots, tests all interactive elements, and produces an evidence-based report listing concrete issues with screenshot references. ## Quick Start Assign this worker a mission to QA the web page at localhost:8000 and produce an evidence-based report with screenshots in public/qa-screenshots.

Frequently Asked Questions about testing-testing-evidence-collector

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I QA a web page with screenshot evidence?▼

Run the Playwright capture script against the target URL to generate responsive, dark mode, and interaction screenshots, then review each image against the original specification. Document every mismatch with a screenshot reference in the evidence-based report template.

How to test accordions and forms with Playwright screenshots?▼

Capture before and after screenshots of each interactive element using automated Playwright interactions, then compare the images to confirm expansion, submission, and validation behavior. Record PASS or FAIL status alongside the test-results.json entry.

Does this QA approach support mobile responsive testing?▼

Yes, it captures screenshots at desktop (1920x1080), tablet (768x1024), and mobile (375x667) viewports and checks mobile navigation such as hamburger menus. Responsive issues are documented with the specific viewport screenshot as evidence.

Why does the QA report default to FAILED status?▼

The methodology assumes first implementations contain 3-5 or more issues, so zero-issue claims are treated as a red flag requiring deeper inspection. Approval requires overwhelming visual evidence that the implementation matches the specification.

What are the limitations of screenshot-based QA testing?▼

Screenshot evidence verifies visual and interactive behavior but does not cover backend logic, security, or load performance. It also depends on the target site being served locally and the Playwright capture script being available.