skills.rest
Dev-Dennis-040
Dev-Dennis-040COMMUNITY
Explore all skills by this author →
GitHub

testing-evidence-collector

Capture and document screenshots to validate UI changes with visual evidence.

10|2|Updated Mar 10, 2026
Search Tags:#automation#screenshots#validation#qa#evidence#bug-reporting#visual-testing
One-click install
npx skills add https://github.com/Dev-Dennis-040/openclaw-agency-skills --skill testing-evidence-collector
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-evidence-collector
Source: https://github.com/Dev-Dennis-040/openclaw-agency-skills/tree/main/skills/testing/testing-evidence-collector
Command: npx skills add https://github.com/Dev-Dennis-040/openclaw-agency-skills --skill testing-evidence-collector

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evidence-based QA requires visual proof to validate software quality and prevent fantasy reporting.

Core Features & Use Cases

  • Evidence-driven QA: captures, reviews, and documents visual results; identifies 3-5 issues per build; emphasizes reality over claims.
  • Step-by-step testing framework: automates reality checks, screenshots, and evidence synthesis for project teams.
  • Use Case: You need to verify a UI builds match the spec and provide visual proof for stakeholders.

Quick Start

Run the Evidence Collector to generate the first validation screenshots and compare results.

Frequently Asked Questions about testing-evidence-collector

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

FAQPage Schema
How do I validate UI changes with screenshots for QA?▼

You can validate UI changes by running an automated evidence collection process that captures deterministic screenshots, compares visual results against specifications, and synthesizes the findings into a structured report.

What is evidence-based bug reporting and why do I need it?▼

Evidence-based bug reporting prevents fantasy reporting by attaching actual visual proof to issue claims. It requires capturing screenshots of software behavior to ensure reported defects reflect reality rather than assumptions.

How do I automate regression checks for web app dashboards?▼

Automate regression checks by executing a standard testing protocol that captures visual evidence across dashboards and admin interfaces, identifying 3-5 issues per build to verify software quality.

Can I use this for acceptance testing across admin interfaces?▼

Yes, the standard testing protocol supports acceptance testing across web apps, dashboards, and admin interfaces by validating UI builds match the spec and providing visual proof for stakeholders.

What is the best way to document visual testing results for stakeholders?▼

Document visual testing results by capturing screenshots, reviewing the visual output, and synthesizing the evidence into a report that emphasizes reality over claims to satisfy stakeholder requirements.

Why does my QA validation lack proof when reporting UI issues?▼

QA validation lacks proof when it skips deterministic screenshot capture. An evidence-driven framework resolves this by automating reality checks and attaching screenshots to every reported issue.

Related Skills

Explore More Software Engineering Skills→
hffmnnjhffmnnj
39

visual-regression

Compare screenshots pixel-by-pixel to detect unintended UI changes.

Community
Intermediate
konneh-hubkonneh-hub

dogfood

Explore web applications to find bugs and produce reports with screenshots and videos.

Community
Advanced
janjaszczakjanjaszczak

mcp-browser-verify

Validate UI flows and reproduce issues with Playwright browser automation.

Community
Intermediate
summarybotngsummarybotng
2

visual-testing-advanced

Detect UI regressions via pixel-perfect screenshot comparison across viewports and browsers.

Official
Advanced