qa-tester

Automate safe QA checks and evidence collection for browser UI, API, and performance tests.

Updated May 8, 2026
One-click install
npx skills add https://github.com/ace3/skills --skill qa-tester-ace3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-tester
Source: https://github.com/ace3/skills/tree/main/skills/qa-tester
Command: npx skills add https://github.com/ace3/skills --skill qa-tester-ace3

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

QA testing for report-only execution of safe checks and evidence capture.

Core Features & Use Cases

  • Browser UI checks, API testing, and exploratory sessions with evidence capture.
  • Retest evidence, and final QA reporting without mutating production data.
  • Safe, non-destructive validation across UI, API, performance, and accessibility checks.

Quick Start

Run a safe, report-only QA check to collect evidence across UI, API, and performance tests.

Frequently Asked Questions about qa-tester

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

FAQPage Schema
How do I automate QA checks without mutating production data?

Non-destructive QA checks validate browser UI sessions, API tests, and performance runs without mutating production data. You execute report-only validation cycles that capture verifiable evidence across exploratory testing and release workflows while adhering to strict output contracts.

Can I collect evidence for UI and API testing in the same workflow?

Yes, evidence collection for UI and API testing can occur in the same workflow. Safe QA checks automate evidence capture across browser UI sessions, REST/GraphQL API tests, and performance runs, consolidating verifiable results for exploratory testing and retest cycles.

What is report-only QA validation and when do I need it?

Report-only QA validation is a non-destructive testing method that executes safe checks and captures verifiable evidence without altering the target system. You need it for exploratory testing, retest cycles, and release validation to ensure quality gates are met safely.

How do I run performance and load testing with verifiable evidence?

Running performance and load testing with verifiable evidence requires automating safe QA checks across load scenarios. The process applies strict output contracts and evidence collection guidelines to capture non-destructive validation results for performance runs.

Does exploratory testing work with automated quality gates?

Exploratory testing works with automated quality gates by applying safe, report-only QA checks to capture verifiable evidence. The automation enforces strict blocking rules and output contracts defined for browser UI sessions and API tests during validation workflows.