The first page returned four correct products. Following the next-page value skipped the remaining eight.
I built this local synthetic API demonstration to show what a small, repeatable API smoke-test pack can catch. The Postman v2.1 collection checks one documented GET endpoint and one unmatched-route probe across ten ordered request scenarios.
Check the whole response contract
Three requests follow the actual nextPage value and check that all twelve products arrive once, in order. Other scenarios check the final page, empty results beyond the dataset, integer boundaries, invalid input and an unknown route. Assertions cover status codes, JSON fields and expected response bodies.
Run it, break it, rerun it
The same collection ran through Newman 6.2.1 in five local executions:
Corrected baseline: 60/60 assertions passed.
Preserved pagination defect: 44/60 passed, 16 failed.
Validation responses changed to HTTP 200: 57/60 passed, 3 failed.
Malformed JSON response: 58/60 passed, 2 failed.
Corrected retest: 60/60 passed.
Each execution made ten requests and evaluated sixty assertions. These are repeated runs of ten scenarios; baseline and retest use the same corrected API. The three negative controls exited with failed assertions, with no transport or script errors.
Inspect and rerun the sample
The pack contains the editable collection, credential-free environments, synthetic API source, setup and Newman commands, and expected-versus-actual reports.
The tested runtime was Node v24.22.1. Postman desktop import was not tested. Authentication, write methods, security, load and production integration testing are outside this sample.
Need a smoke pack for your API?
My existing Postman API smoke-test service starts with non-sensitive API documentation and agreed expected results. Message through the service page with a small example so we can confirm the scope and safe test environment.
postman-smoke-demo.zip
