API Test Automation Pro

What Problem It Solves

Many API test setups remain fragmented: login, CRUD, pagination, OpenAPI parsing, 429 retries, Mock services, and reports each use different tools. This skill folds common API testing tasks into one keyword-driven route table, then moves through design, execution, and reporting phases. It is aimed at engineering teams that want interface tests to be repeatable, inspectable, and report-ready rather than ad hoc script runs.

How It Works

The core model is progressive routing with confirmation gates:

• Test design: keywords such as login, registration, pagination, or CRUD route to SmartTestParser or TestAnalyzer, producing test points and use-case structure first.
• Execution and diagnostics: RestClient and GraphQLClient handle requests; timeouts, 429, 500, and auth failures fall back to DiagnosticAnalyzer for retries, Retry-After handling, and token refresh.
• Validation and reporting: ContractTester checks OpenAPI or JSON Schema contracts, while TestReporter generates HTML or Allure output; batch runs must end with a report.

Boundaries

• It assumes a Python stack with Python 3.8+, requests, httpx, and pytest.
• If keywords miss the route, fall back to references/route_table_full.md or select modules manually.
• Performance and load tests are progressive, so default settings should not be treated as final capacity evidence.
• For security-sensitive, production-data, or write-heavy flows, still confirm scope and output paths before running.