qa-phase3

Run API and browser tests from test-cases.json with real-time status updates.

9|3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Pythagora-io/agent-templates --skill qa-phase3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-phase3
Source: https://github.com/Pythagora-io/agent-templates/tree/main/QA%20Agent/qa-phase3
Command: npx skills add https://github.com/Pythagora-io/agent-templates --skill qa-phase3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams need to run every test case across API and browser sections defined in test-cases.json, updating status and collecting evidence in real time.

Core Features & Use Cases

  • Execute all API tests and all browser tests from test-cases.json, updating statuses and notes as tests complete
  • Enforce strict rules to verify screenshots before marking pass, ensuring UI correctness
  • Read environment-specific values from environment.md and align with the testing-plan.md companion

Quick Start

Run API and browser tests defined in test-cases.json and report results in real time.

Frequently Asked Questions about qa-phase3

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

FAQPage Schema
How do I automate running API and browser tests with real-time status updates?

QA automation executes API and browser tests defined in test-cases.json, updating statuses and capturing evidence in real time. It reads environment-specific values from environment.md and aligns execution with testing-plan.md.

What is the best way to ensure browser UI test correctness during automated QA workflows?

The best way to ensure browser UI correctness is using a QA workflow that enforces strict screenshot verification before marking a test as passed. This captures visual evidence and prevents false positives in browser tests.

Do I need an environment configuration file to run end-to-end API and browser tests?

Yes, you need an environment.md file to provide environment-specific values and a testing-plan.md file as a reference. These files configure the context needed to execute end-to-end API and browser tests accurately.

How does real-time test evidence capture work for API and browser automation?

Real-time test evidence capture works by executing tests sequentially from test-cases.json and updating the file with statuses, notes, and verified screenshots immediately after each API or browser test completes.

Can I execute both backend API and frontend browser tests from a single test-cases JSON file?

Yes, you can execute both backend API and frontend browser tests from a single test-cases.json file. The automation reads all defined test cases, runs them, and reports live results with collected evidence for each section.

Why are my automated browser tests passing when the UI is broken?

Automated browser tests pass with a broken UI if the workflow lacks strict screenshot verification rules. You need a QA process that enforces visual evidence validation before allowing a test status to be marked as passed.