Mid-LevelAPI & Integration Testing
Explain how you would use Postman for API testing beyond simple requests.
- Postman
- API tools
- test organization
Answer it first, then compare. Nothing here is saved or scored.
Model answer
Beyond basic requests: (1) Collections, organize tests by feature/workflow. (2) Pre-request scripts - dynamic data generation, token refresh. (3) Tests tab - JavaScript assertions on status, body, headers, response time. (4) Environments - switch between dev/staging/prod variables. (5) Collection runner - run all tests sequentially with data files (CSV/JSON). (6) Newman - CLI runner for CI integration. (7) Monitors - scheduled runs for production API health checks.
What interviewers listen for
- Schema-first thinkingYou validate response shape before you assert on values, every time.
- Status-code literacyYou can defend why 401 vs 403 vs 422 matters for the consumer.
- Contract awarenessYou know when consumer-driven contract tests beat end-to-end checks.
- Auth fluencyYou can describe rotating tokens across parallel workers without secrets in logs.