QA Test Runner Skill

Automate QA validation by running Playwright UI tests and curl + jq API checks against your target application to verify ticket acceptance criteria. The skill reads the criteria, identifies test modes, executes the checks, and outputs structured pass/fail documentation.

Yes, you can generate pass/fail reports with evidence capture by running automated UI and API verifications. The skill saves screenshots and API responses under a standardized /home/agent/evidence directory for full traceability and reporting.

Yes, you need Playwright, curl, and jq installed to execute the end-to-end test automation. These tools are required dependencies for performing UI checks and extracting API responses during the validation process.

Automated API testing with curl and jq handles ticket-driven workflows by extracting the target URL directly from the ticket, executing curl requests, and parsing JSON responses with jq. This validates acceptance criteria and generates standardized pass/fail outcomes.

The best way to automate evidence collection during sprint QA testing is to run automated UI and API checks that save screenshots and API responses automatically. This standardizes naming conventions for traceability across development sprints.

You should not use automated Playwright and curl API checks for QA validation if your ticket-driven workflow does not require both UI and API verification, or if your application lacks a target URL accessible for end-to-end testing.