Postman Pagination, Filtering and Error Case Test Set
Cover list endpoints thoroughly.
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.
Write a test set for a list endpoint. Endpoint and parameters (page, limit, sort, filters): [ENDPOINT_AND_PARAMETERS]. Documented behaviour: [DOCUMENTED_BEHAVIOUR]. Example response: [EXAMPLE_RESPONSE]. Write a table with Test, Request, Expected status, Expected body check and Why it matters, covering at least twelve cases: default page size, a custom limit, the last page, a page beyond the end, limit zero, very large limits, invalid values, sort order including stable sorting when values tie, combined filters, no matches, the maximum page size, the error body format, and consistency of totals across pages. Data setup: create 25 test records so a page size of 10 gives 3 pages with 10, 10 and 5 items (10 + 10 + 5 = 25). Filter expectations, for example status equals open returns 9 records and status equals open and priority equals high returns 3. Script outline in words: request page 1 with limit 10, store the next link or page number, loop until no more pages, collect IDs, then assert the number of IDs equals the reported total and there are no duplicates; write it in Postman's scripting style and mark the syntax [VERIFY]. Note performance expectations and rate limits. Each test has a clear pass or fail, does not depend on production data, and runs only against a non-production system.
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.