qa-evidence

Standardize QA evidence capture and report formatting for testing documentation.

2|1|Updated May 27, 2025

Search Tags:#testing #screenshots #qa #reporting #evidence #regression #sign-off

Ready to run

npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-evidence

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-evidence
Source: https://github.com/VirtoCommerce/vc-mcp-testing-module/tree/main/skills/qa-evidence
Command: npx skills add https://github.com/VirtoCommerce/vc-mcp-testing-module --skill qa-evidence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent QA artifacts by defining when to capture evidence, how to format reports, and where testing outputs should be stored.

Core Features & Use Cases

Evidence Capture Standards: Guides screenshot, console log, network trace, and failure evidence collection rules during testing sessions.
Report Formatting Guidance: Provides compact, detailed, and sign-off reporting structures for different QA review scenarios.
Artifact Organization: Enforces correct output paths and naming conventions for test documentation, bug evidence, regression reports, and browser artifacts.

Quick Start

Use the qa-evidence skill to prepare the evidence capture policy and reporting standards before starting a QA test session.

Frequently Asked Questions about qa-evidence

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

FAQPage Schema

How do I standardize QA evidence capture and reporting formats for regression testing?▼

You can standardize QA evidence capture by applying rules for screenshots, console logs, and network traces, ensuring consistent test documentation and bug reporting outputs across sessions.

What is the best way to organize test documentation and bug evidence artifacts?▼

Organize test documentation by enforcing strict artifact naming conventions and output path requirements for bug evidence, regression reports, and browser artifacts to prevent inconsistent storage.

How do I structure QA reporting for different stakeholder review scenarios?▼

Structure QA reporting by selecting from compact, detailed, or sign-off reporting tiers to match the verbosity requirements of different stakeholder sign-off and validation scenarios.

When do I need to apply screenshot rules and verbosity tiers in software testing sessions?▼

Apply screenshot rules and verbosity tiers during software quality assurance sessions involving test execution, regression validation, and bug reporting to maintain consistent testing documentation.

Can I use this approach for stakeholder sign-off reporting without external dependencies?▼

Yes, you can generate standardized sign-off reporting structures directly, as the approach operates without external dependencies to guide artifact organization and failure evidence collection.