test-case-execution-assistant

Executes structured test cases via curl and Playwright and records standardized results.

2|Updated May 30, 2026
One-click install
npx skills add https://github.com/opensourceways/integration-tests --skill test-case-execution-assistant-opensourceways
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-case-execution-assistant
Source: https://github.com/opensourceways/integration-tests/tree/main/test_skills_base/test-case-execution-assistant
Command: npx skills add https://github.com/opensourceways/integration-tests --skill test-case-execution-assistant-opensourceways

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually executing test cases and recording results is repetitive and error-prone, especially when mixing API tests, UI tests, and human-reported observations. This Skill acts as a dedicated test execution engineer: it takes your structured test cases, runs them step by step with real tools, and outputs a standardized execution record without inventing results. ## Core Features & Use Cases - Strict Step-by-Step Execution: Validates preconditions first (marking cases as blocked when unmet), then executes each numbered step without merging, skipping, or reordering. - Real Tool-Based Verification: Runs API cases via curl/Bash and UI cases via Playwright, including automated execution of agent-exec YAML blocks with placeholder injection, response capture, and assertion evaluation. - Four-State Judgment & Defect Logging: Classifies each case as passed, failed, blocked, or not executed, and records defects with phenomenon, deviation, severity level (critical to suggestion), and fix direction. - Standardized Reporting: Outputs a fixed 7-column Markdown table plus execution summary, and can save a full report file with defect, blocked, and unexecuted lists. - Use Case: Paste a batch of API test cases exported from Jira; the assistant runs each curl request, compares responses against expected assertions, and returns a complete execution table with pass rate and defect statistics. ## Quick Start Execute the test cases in my attached file and give me the execution record table with pass/fail status and defect details.

Frequently Asked Questions about test-case-execution-assistant

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

FAQPage Schema
How do I execute test cases automatically with an AI assistant?▼

Provide structured test cases containing a case ID, preconditions, numbered steps, and expected results. The assistant validates preconditions, executes each step using curl for API cases or Playwright for UI cases, and returns a 7-column Markdown execution table with status and defect details.

How to run API test cases with curl assertions?▼

Define steps with request method, URL, headers, and body, plus assertions like http_status or jsonpath equals checks. The assistant builds the curl command, captures the HTTP status code and response body, and evaluates each assertion to determine pass or fail.

What input formats does test case execution support?▼

Supported formats include Markdown tables, plain-text numbered step lists, Excel or CSV pastes, exports from ZenTao, Tapd, or Jira, and cases containing agent-exec YAML blocks for fully automated execution. Missing fields are flagged as not executed rather than guessed.

Can it execute UI test cases with Playwright?▼

Yes, UI steps in agent-exec blocks map to Playwright actions such as navigate, fill, click, and screenshot. Assertions on URL, visible text, element state, and storage are evaluated through Playwright evaluation calls.

What happens when test case preconditions are not met?▼

The case is marked as blocked and subsequent steps are skipped, with the blocking reason recorded in the defect column. Blocked cases are listed separately in the execution summary and do not count toward pass or fail statistics.

What are the limitations of automated test case execution?▼

It only executes provided cases and never designs, modifies, or completes them. Cases with vague expected results like "displays normally" are marked not executed, and without tool access or user-supplied observations no real results can be produced.