executing-qa-test-suite

Execute a planned QA test roster against a running system and emit a results-backed PASS, FAIL, or ERROR gate.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/Jin9/skillify-foundation --skill executing-qa-test-suite-jin9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executing-qa-test-suite
Source: https://github.com/Jin9/skillify-foundation/tree/main/treasury/executing-qa-test-suite
Command: npx skills add https://github.com/Jin9/skillify-foundation --skill executing-qa-test-suite-jin9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? A test plan alone proves nothing — someone must run the planned roster against a live system, measure real coverage, catch flaky tests and live defects, and produce an evidence-backed sign-off verdict instead of an unverified claim of success. ## Core Features & Use Cases - Roster Execution: Runs each planned test item against a reachable target environment via a CI/test runner using a Plan-Act-Verify loop, capturing real pass/fail evidence. - Coverage & Flakiness Measurement: Reads line/branch coverage from the runner report and re-runs suspect items to flag non-deterministic tests rather than passing them by luck. - Gated Verdict: Emits a schema-validated PASS, FAIL, or ERROR verdict with totals, defects, flaky items, and an audit ID, routing failures to a fixer and a human verification layer. - Use Case: After a banking test plan is produced, run the full roster against a staging sandbox and receive a FAIL verdict with severity-classified defects and reproduction evidence for human sign-off. ## Quick Start Execute the QA test roster from my qa-plan against the staging environment and produce the pass/fail gate with measured coverage.

Frequently Asked Questions about executing-qa-test-suite

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

FAQPage Schema
How do I execute a QA test suite against a running system?▼

Provide the planned test roster, a reachable target environment, and an idempotency key. Each roster item runs through a Plan-Act-Verify loop via the CI/test runner, capturing real pass/fail evidence rather than self-declared results.

How to measure test coverage on a running system?▼

Coverage is read directly from the runner report as line/branch coverage on the live target, never from a self-declared figure. If coverage cannot be measured, the skill reports that instead of inferring a pass.

How are flaky tests handled during QA execution?▼

Suspect items are re-run a bounded number of times; if results differ, the item is marked flaky and excluded from a PASS. Flaky items are reported separately for stabilization rather than passed by luck.

When should I not use this QA execution skill?▼

Do not use it to design the test plan, run a single test level in isolation, or write and fix tests or production code. It only executes an existing roster and reports a verdict; failures route to a separate fixer.

What happens when a required QA test fails?▼

A failed required item or unmet signoff criteria produces a FAIL verdict with severity-classified defects and reproduction evidence. The failure routes to a bug-diagnosis stage and a named human verification layer, never auto-approving.