菜单
Runs the AI-powered REST Assured test generator with an OpenAPI/Swagger spec path, then directs the user to the generated test files. Use when the user wants to generate API tests from a spec, points at an OpenAPI file, or says "generate tests for this spec."
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Adds authentication (Bearer token, Basic, or API key) to API tests using config or env and a shared RequestSpecification. Use when the user wants to add auth to tests, use a token, or secure requests.
Adds negative API test cases (400, 404, 401, etc.) to an existing test class following project rules. Use when the user wants to add negative tests, cover error cases, or add 404/400 tests.
Adds request and response logging to API tests using Rest Assured's log() (e.g. ifValidationFails) without exposing secrets. Use when the user wants to add logging, debug requests, or log on failure.
Debugs and fixes a failing API test by inspecting assertions, status code, response body, and environment. Use when a test fails, the user pastes a failure message, or they ask why a test is failing.
Extracts common setup (base URI, auth, RequestSpecification) from multiple test classes into an abstract base class. Use when the user wants to reduce duplication, add a base test class, or share setup across test classes.
Runs the project's API tests with Maven. Use when the user wants to run tests, run the test suite, run smoke tests, or verify tests after changes.
| name | generate-api-tests-from-spec |
| description | Runs the AI-powered REST Assured test generator with an OpenAPI/Swagger spec path, then directs the user to the generated test files. Use when the user wants to generate API tests from a spec, points at an OpenAPI file, or says "generate tests for this spec." |
Use this skill when the user:
Identify the spec file.
Use the file the user pointed at or the path they gave (e.g. src/main/resources/sample-specs/amadeus-flight-most-traveled-destinations.json or a path under sample-specs/).
Run the generator from the project root.
From the ai-rest-assured-framework project root, run:
mvn exec:java -Dexec.args="--spec <path-to-spec>"
Example:
mvn exec:java -Dexec.args="--spec src/main/resources/sample-specs/amadeus-flight-most-traveled-destinations.json"
For Claude instead of OpenAI, add -p claude (and set ANTHROPIC_API_KEY).
Interactive steps.
The CLI will: read the spec, send it to the LLM for test cases, print them for review, and ask for approval (Y/n). After the user approves, it generates REST Assured + TestNG code.
Generated output.
Generated test classes are written under src/test/java/ (default), typically in a generated/ package. Tell the user to open the new file(s) there to review. Example path: src/test/java/com/qa/api/tests/generated/.
OPENAI_API_KEY or ANTHROPIC_API_KEY set to use the generator.src/main/resources/sample-specs/ when using bundled specs.