API Test Plan From an Endpoint List With Assertions and Negative Cases
Plan tests for an API using collections, environments and assertions.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Plan API tests in Postman. The endpoints with methods, parameters and expected responses: [ENDPOINT_LIST]. Authentication method: [AUTH_METHOD]. Environments (development, staging): [ENVIRONMENTS]. Known rules (limits, validation): [API_RULES]. Produce a collection structure (folders by resource), environment variables (base URL, token placeholder, ids), a naming convention, and for each endpoint a set of tests: success, missing required field, invalid type, boundary values, unauthorised, not found, and rate or size limits. Write the assertions in plain words (status code, response time threshold I set, schema fields, error message format) and example test scripts in JavaScript with comments, marked [VERIFY] for my version. Add a data-driven test idea, a sequence for create, read, update, delete with cleanup, and a report summary template with pass counts and percentages. Use test data and test environments only; never real credentials or production data. Add a worked example for POST /orders: valid body expects 201 and an id, missing quantity expects 400 with a message naming the field, quantity -1 expects 400, no token expects 401, repeated request with the same idempotency key expects the same order; include the test list as a table with expected results.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.