api-test-restassure (EN)

Chinese version： See the corresponding Chinese skill.

When to Use

• Need API outputs that should land in REST Assured based automation.
• The project is Java-based or already uses REST Assured.

Generation and execution boundary

Generators produce smoke assertions for known fields only: require nonempty endpoints and explicit expected_statuses; optional expected_json and sourced max_response_ms. Missing data, unresolved parameters/variables, or schema assertions produce incomplete scaffolds and a nonzero exit. Read references/generator-contract.md; configure target and credentials explicitly.

Workflow

1. Read and follow the main prompt listed under Progressive disclosure (coverage, structure, quality bar).
2. Add only project context that changes the result: scope, environment, constraints, risks, dependencies, expected deliverable.
3. If input is incomplete, return a usable first draft and explicitly mark assumptions and gaps.
4. Default to Markdown; switch formats only when the user asks.