APITester Agent-Driven API Testing

Execute YAML-defined API tests and generate formatted result reports.

1|1|Updated Mar 25, 2026

Search Tags:#automation #testing #documentation #api #yaml #http

Ready to run

npx skills add https://github.com/penghang1223/niannian-workspace --skill apitester-agent-driven-api-testing

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: APITester Agent-Driven API Testing
Source: https://github.com/penghang1223/niannian-workspace/tree/main/openclaw-api-tester
Command: npx skills add https://github.com/penghang1223/niannian-workspace --skill apitester-agent-driven-api-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

API testing is often manual, slow, and error-prone. APITester enables defining tests in plain English, running them, and automatically documenting results.

Core Features & Use Cases

YAML-based test definitions that require no coding
Variable chaining to reuse response data across requests
Environment configs for dev, staging, and prod
Auto-documentation to generate reports from test results
Parallel execution for faster test runs
Multi-format reporting (HTML, JSON, Markdown)

Quick Start

Describe tests in YAML and run them to generate a formatted results report.

Frequently Asked Questions about APITester Agent-Driven API Testing

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

FAQPage Schema

How do I run API tests without writing code?▼

YAML-based API testing allows you to define HTTP requests and assertions in plain text without writing code, enabling you to execute tests and validate responses through structured configuration files.

How do I generate API test documentation automatically?▼

Automatic API test documentation is generated from executed test results, producing multi-format reports in HTML, JSON, and Markdown to provide formatted outputs of your HTTP request outcomes without manual formatting.

Can I reuse response data across multiple HTTP API requests?▼

Yes, you can reuse response data across HTTP API requests using variable chaining, which extracts values from previous API responses and passes them into subsequent requests within your YAML test definitions.

Does this API testing approach support separate dev, staging, and prod environments?▼

Yes, this API testing approach supports separate dev, staging, and prod environments through environment configs, allowing you to switch base URLs and variables across different deployment targets without altering test definitions.

What is the best way to speed up HTTP API test execution?▼

The best way to speed up HTTP API test execution is using parallel execution, which runs multiple YAML-defined test cases simultaneously to reduce total testing time and accelerate result reporting.

Do I need coding skills to define HTTP API tests in YAML?▼

No, you do not need coding skills to define HTTP API tests in YAML, as the framework uses plain English descriptions and structured configuration files to author and execute test cases without programming.