Unlock Postman's Hidden Power: Automate API Tests Like a Pro

Postman's most underrated feature: unbeatable API test automation efficiency!

This article assumes readers already know basic Postman usage and can send simulated requests.

Current environment

Windows 7 - 64

Postman version (free): Chrome App v5.5.3

Different UI versions may vary slightly.

To achieve automated API testing, we need to address three questions:

How to determine if an API request succeeded

How to perform batch and scheduled testing

How to handle dependent APIs (e.g., login required before order)

We will cover three parts to solve these.

API result evaluation

Automation requires tools or code to judge results. Two main approaches:

Check if the returned code matches expectation

Check if the response body contains expected keywords

Postman provides a Tests panel where JavaScript can be used for assertions.

Feature area

The Tests feature uses JavaScript; Postman also offers code snippets for common assertions.

Scripts

Postman exposes variables: responseCode, responseBody, tests, key, value.

These allow you to evaluate request outcomes. responseCode: contains status information (e.g., code) responseBody: response data as string tests: key‑value pairs indicating test results key: description of result (e.g., "code 200") value: boolean, true for pass, false for fail

Additional useful variables: responseTime: request duration postman.getResponseHeader(name): get response header postman.setGlobalVariable(key,value): set global variable

Code snippets

Postman's Snippets provide ready‑made scripts. Examples:

// Status code is 200
tests["Status code is 200"] = responseCode.code === 200;

// Body contains string
tests["Body matches string"] = responseBody.has("your keyword");

// Body equals string
tests["Body is correct"] = responseBody === "expected content";

// JSON value check
var jsonData = JSON.parse(responseBody);
tests["Your test name"] = jsonData.value === 100;

// Response time less than 200ms
tests["Response time is less than 200ms"] = responseTime < 200;

These cover single‑request validation.

Collection (batch) testing

Save multiple requests in a Collection to run them together.

Run the collection with a simple test that checks if the status code is 200.

tests["Status code is 200"] = responseCode.code === 200;

Batch execution

Click Run to open the runner where you can set environment, iteration count, delay, and data file. Environment: switch target environment Iteration: number of times to run Delay: pause between requests (ms) Data File: upload CSV/JSON data for variables

Variable data

Static parameters limit test value diversity. Use a CSV file with columns username,password to supply different credentials.

username,password
test1,123456
test2,222222
test3,123456
test4,444444

Postman maps these columns to variables {{username}} and {{password}} in the request.

Pre‑request script

Set variables before each request:

postman.setGlobalVariable("username", "test1");
postman.setGlobalVariable("password", "123456");

For data‑driven testing, use the Data File instead of hard‑coded values.

Scheduled tasks

Postman's Monitors allow you to run a collection on a timer (e.g., hourly).

Request dependency handling

When an API depends on a previous call (e.g., login token), ensure execution order, store the token in an environment variable, and reference it in subsequent requests.

Example Test script for login request:

if (responseCode.code === 200 && responseBody.has("access_token")) {
    tests["login"] = true;
    var jsonData = JSON.parse(responseBody);
    postman.setEnvironmentVariable("token", jsonData.result.access_token);
    postman.setNextRequest("Request3");
} else {
    tests["login"] = false;
}

In the dependent request, use {{token}} in headers or body.

Running the collection validates the flow: Request1 (login) and Request3 succeed, Request2 is skipped, Request4 runs.