菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | add-request-response-logging |
| description | 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. |
Use this skill when the user:
Prefer log on failure.
Add .log().ifValidationFails() to the request spec (or to given()) so request and response are logged only when a test fails. Keeps CI output clean.
Optional: log body only.
Use .log().ifValidationFails(LogDetail.BODY) to limit logged detail. Use .log().body() only for local debugging; remove or guard with a flag before committing if noisy.
Never log secrets.
Do not log headers or body that contain Authorization, API keys, or passwords. If using custom logging or filters, strip or redact sensitive fields. Follow project rule: never log secrets.
Where to add.
RequestSpecification in @BeforeMethod or base class so all tests get it, orgiven().log().ifValidationFails().when()...Verify.
Run a test that fails on purpose (e.g. wrong status code) and confirm logs show request/response. Confirm auth header or body is not printed in plain text.
log().ifValidationFails(); avoid log().all() on every request in CI. Use TestNG and assertions for outcomes, not System.out for important checks.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.
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.
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."
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.