skills.rest
dwoolworth
dwoolworthCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-runner

Run Playwright UI tests and curl + jq API checks on ticket targets.

1|Updated Feb 6, 2026
Search Tags:#testing#qa#evidence#playwright#jq#api-testing#curl
One-click install
npx skills add https://github.com/dwoolworth/devteam --skill test-runner-dwoolworth
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-runner
Source: https://github.com/dwoolworth/devteam/tree/main/templates/skills/qa/test-runner
Command: npx skills add https://github.com/dwoolworth/devteam --skill test-runner-dwoolworth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

QA teams spend significant time manually validating tickets across UI and API. This skill automates the validation by running Playwright-based UI checks and curl + jq API verifications, reducing cycle time and ensuring acceptance criteria are met.

Core Features & Use Cases

  • Playwright browser testing to validate UI elements, user flows, and navigation.
  • API testing with curl + jq to verify endpoints, status codes, and response payloads.
  • Mixed-mode testing where criteria require both UI and API checks, with automatic mode selection.
  • Evidence generation and reporting with consistent file naming and storage under /home/agent/evidence/{TICKET_ID}.
  • Target URL extraction from ticket comments to locate the running instance.

Quick Start

Invoke the QA test runner on a ticket to execute Playwright UI tests and API checks against the ticket's target URL, saving evidence under /home/agent/evidence/{TICKET_ID}.

Frequently Asked Questions about test-runner

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

FAQPage Schema
How do I automate QA validation for tickets with mixed UI and API acceptance criteria?▼

Automating mixed UI and API validation involves running Playwright UI checks and curl + jq API verifications on ticket targets. The process applies automatic mode selection to execute tests and generate standardized evidence stored under /home/agent/evidence/{TICKET_ID}.

Can I run Playwright browser tests and curl API checks on the same target URL?▼

Yes, running Playwright browser tests and curl API checks on the same target URL is supported. The skill extracts the target URL from ticket comments and executes both UI and API validations, satisfying mixed-mode acceptance criteria.

What is the best way to generate standardized test evidence for automated QA runs?▼

Generating standardized test evidence requires consistent file naming and storage under /home/agent/evidence/{TICKET_ID}. The QA test runner automates this by producing evidence reports during Playwright and curl + jq test execution.

How do I extract a target URL from ticket comments for API testing with curl and jq?▼

Extracting a target URL from ticket comments is handled automatically by the test runner. It locates the running instance from the ticket data and passes the URL to curl + jq for API endpoint verification and response payload checks.

Do I need to manually select between UI and API testing modes for ticket validation?▼

No, manual mode selection is not required. The validation process applies automatic mode selection based on the ticket's mixed UI and API acceptance criteria, orchestrating Playwright and curl + jq tests accordingly.

Related Skills

Explore More Software Engineering Skills→
dwoolworthdwoolworth
1

QA Test Runner Skill

Automate end-to-end QA validation with Playwright UI tests and curl + jq API checks.

Community
Advanced
luicabref97luicabref97

fpf:query

Search and aggregate FPF knowledge base hypotheses with assurance scores.

Community
Intermediate
ITSaltITSalt
23

nacl-tl-qa

Automate end-to-end QA testing of UC tasks with MCP Playwright.

Community
Advanced
marcmontecalvomarcmontecalvo

bmad-qa-generate-e2e-tests

Generate API and end-to-end tests from existing project test frameworks.

Community
Advanced