You sent a request. Got a 200 back. Response looks fine. You move on. Next day, the developer changes the response format. You send the same request. Still 200. But the "email" field is now called "emailAddress." Your frontend breaks in production. Nobody caught it.
That's the problem with manual checking. Your eyes are not assertions. You glance at the response and think "looks good." But you didn't actually verify that every field exists, every type matches, every value is within range. You were the security guard waving people through without checking IDs.
Key Point: Postman tests are JavaScript assertions that run automatically after every request. You write them once, and they guard your API forever. No manual inspection needed.
Every request in Postman has a "Scripts" tab (it was called "Tests" tab in older versions). Inside it, there are two sections: "Pre-request" and "Post-response." Your test assertions go in the Post-response section. They execute right after the response comes back — before you even see it on screen.
Think of it this way. You're not just sending requests anymore. You're building a test suite — one request at a time. Every request you save with assertions becomes a regression test that you can run forever.
A QA engineer at a fintech company had 200 API endpoints. No tests. Every release, the team manually checked 50 critical endpoints. Took 3 hours. They still missed bugs. After adding Postman tests — 200 endpoints, all tested in 2 minutes via Collection Runner. Bug count dropped 60% in one quarter.
Start small. Pick your 5 most important endpoints — login, get user, create order, payment, logout. Add tests to those first. Then expand. You don't need to test everything on day one.
Q: Why do we write automated tests in Postman instead of just checking responses manually?
A: Manual checking is unreliable — humans miss things, especially under pressure. Automated tests run the same assertions every time, catch regressions instantly, and can be executed as part of Collection Runner or CI/CD pipeline via Newman. They also serve as living documentation of expected API behavior. When a field changes or a status code shifts, the test fails immediately and tells you exactly what broke.
Key Point: Postman tests automate what your eyes cannot reliably do — verify every field, every type, every status code, every single time.