Prompt Api Tests

# Prompt — API tests

> [🇷🇺 Русский](../ru/prompt-api-tests.md) · 🇬🇧 **English**

[← Index](./README.md) · [Standards](./standards.md) · [Template](./template.md)

tags: #prompt #api-testing #qa #backend #service #single-shot
**Status:** `🟢 Ready`
**Owner:** Pandamy619
**Last edit:** 2026-05-20
**Version:** v1
**Source idea:** [LogicBalls — API Test Scenario Builder](https://logicballs.com/ai-prompt/prompts/api-test-scenario-builder)
**Delta from original:** added a summary risk overview and coverage table up front, explicit assertion requirements, and the canonical "behavior when context is missing" block.

---

## When to use

- When you need to derive a test set from an OpenAPI or endpoint description quickly
- When you can't afford to forget negative cases, auth, edge cases, and contract checks
- When you need to prepare a base for manual tests, BDD, or automation

## What to substitute

- `{{api_specification}}` — string or link, e.g. `OpenAPI 3.1 at /api/openapi.yaml` or inline spec text
- `{{auth_method}}` — enum: `jwt | oauth2 | api_key | mtls | none`
- `{{test_focus_areas}}` — enum: `functional | security | performance | contract | all`
- `{{output_format}}` — enum: `bdd | manual | json | csv`
- `{{risk_level}}` — enum: `low | medium | high | critical`
- `{{environment_constraints}}` — string, e.g. `test Postgres seed; do not call prod providers`

## Definition of done

Universal minimum — see [Definition of done](./standards.md#2-definition-of-done).

Specific criteria:

- All 9 scenario groups are covered (positive, negative, auth, boundary, rate limit, contract, errors, idempotency, integrations), or it's explicitly stated why a group is not applicable
- Each test has all 6 fields filled (name, preconditions, steps, data, expected result, priority)
- Steps include concrete assertions (`status_code == 404`, `body.error == "..."`), not "check the response"
- The risk summary lists 3-5 key risks

## Prompt