Default and conditional responses in Postman - Framework Patterns

Framework Mode - Default and conditional responses

Folder Structure

postman-project/
├── collections/
│   └── api-collection.json          # Main Postman collection with requests and tests
├── environments/
│   ├── dev.postman_environment.json # Dev environment variables
│   ├── staging.postman_environment.json
│   └── prod.postman_environment.json
├── scripts/
│   ├── pre-request-scripts.js       # Shared pre-request scripts
│   └── test-scripts.js              # Shared test scripts for assertions
├── mocks/
│   └── default-response.json        # Default mock response definitions
├── README.md
└── postman.config.json               # Optional config for CI integration

Test Framework Layers

• Collections: Group of API requests with tests and scripts.
• Environments: Variables for different setups (dev, staging, prod).
• Pre-request Scripts: Code run before requests to set variables or conditions.
• Test Scripts: Assertions to check responses, including conditional checks.
• Mock Servers: Simulate default or conditional responses for testing without real backend.
• Utilities: Shared scripts or helper functions for reuse.

Configuration Patterns

• Environment Variables: Store base URLs, tokens, and flags to switch between environments.
• Conditional Logic in Tests: Use JavaScript in test scripts to check response codes or body and assert accordingly.
• Default Responses in Mocks: Define fallback responses in mock servers for unmatched requests.
• Collection Variables: Use for values shared across requests and tests.
• CI Integration: Use Newman CLI with environment files to run tests automatically.

Test Reporting and CI/CD Integration

• Newman Reports: Generate JSON, HTML, or JUnit reports from test runs.
• CI Pipelines: Integrate Newman runs in Jenkins, GitHub Actions, or GitLab CI to run tests on code changes.
• Conditional Test Outcomes: Tests can pass or fail based on conditional assertions in scripts.
• Slack or Email Notifications: Send reports or alerts on test failures.

Best Practices

• Use environment variables to avoid hardcoding URLs or credentials.
• Write clear conditional assertions to handle different response scenarios.
• Use mock servers to test default and fallback responses without backend dependency.
• Keep test scripts modular and reusable by placing common logic in shared scripts.
• Integrate automated tests in CI/CD pipelines for continuous feedback.

Self Check

Where would you add a new test script that checks for a conditional response status code in this framework structure?

Key Result

Organize Postman tests with collections, environments, scripts, and mocks to handle default and conditional API responses effectively.