Plan an API test suite for my service
Plans an API test suite for a service you own, covering contract, errors, auth, limits and data, ordered by risk.
Task:
Plan an API test suite for my service that I can build in [time available].
Context:
The API is [REST, GraphQL or other] built with [stack] with about [number of endpoints] endpoints. The riskiest parts are [riskiest parts]. I test in [environment, never production] and my team has [team size] people.
Rules:
- Group tests as contract and schema, success paths, error and edge cases, authentication and permissions, rate limits, and data cleanup.
- Pick the 5 endpoints to cover first and say why, using the risk I named.
- Say what each group needs, such as test accounts, seed data or a mock of a third party, and keep real customer data out of tests.
- Run tests only against environments I own, and do not store secrets in the test files. Use environment variables.
- Keep tool names generic unless I give one.
Result:
A table with the columns group, what it checks, example case and tool type, then a numbered build order of at most 6 steps.