How Apifox Solves Swagger’s API Testing Pain Points with Automated Scripts

In many projects Swagger is used for documenting APIs, but in production environments the documentation is often disabled for security, forcing developers to copy Swagger definitions to Postman for testing, which is cumbersome.

Common problems include frequent changes in the development environment that Swagger can’t keep up with, mismatched front‑end/back‑end contracts that prevent Swagger from mocking data, and the need to run pre‑ and post‑scripts for authentication, which Swagger does not support.

Apifox Features

Apifox addresses these issues with the following capabilities:

One‑click import of Swagger JSON (e.g., http://localhost:6091/v2/api-docs) and Postman collections (Collection v2.1).

Environment and variable management for multiple environments (dev, test, prod) allowing dynamic domain switching and global variables such as tokens.

Global parameters supporting Header, Cookie, Query, and Body (form‑data and x‑www‑form‑urlencoded only).

Pre‑script for automatic login: a script checks for a valid token, fetches a new one if missing or expired, and stores it in environment variables.

Post‑script for handling login failures by re‑triggering the login request.

Cookie extraction script to capture Set‑Cookie headers and store specific cookies (e.g., XSRF‑TOKEN) as environment variables.

Signature script for APIs that require request signing.

Mock data generation: define request/response schemas and mock rules to automatically produce example requests and responses, usable locally or in the cloud.

cURL import: convert captured network traffic (e.g., from Charles) into executable requests.

Automation testing integration (future work).

Sample Pre‑Login Script

function sendLoginRequest() {
  const baseUrl = pm.environment.get("BASE_URL");
  const username = pm.environment.get("LOGIN_USERNAME");
  const password = pm.environment.get("LOGIN_PASSWORD");
  const loginRequest = {
    url: baseUrl + "/mobile/auth/login",
    method: "POST",
    header: { "Content-Type": "application/json" },
    body: {
      mode: "raw",
      raw: JSON.stringify({ username, password })
    }
  };
  pm.sendRequest(loginRequest, function (err, res) {
    if (err) { console.log(err); return; }
    const jsonData = res.json();
    pm.environment.set("ACCESS_TOKEN", jsonData.data.token);
    pm.environment.set("ACCESS_TOKEN_EXPIRES", jsonData.data.tokenExpire);
  });
}
if (!pm.environment.get("ACCESS_TOKEN") ||
    (pm.environment.get("ACCESS_TOKEN_EXPIRES") &&
     new Date(pm.environment.get("ACCESS_TOKEN_EXPIRES")) <= new Date())) {
  sendLoginRequest();
}

Sample Post‑Login Failure Script

var jsonData = pm.response.json();
if (jsonData.errcode !== 0 && jsonData.errmsg === "无效用户") {
  sendLoginRequest();
}

Cookie Extraction Script

var setCookie = postman.getResponseHeader("Set-Cookie");
var cookies = setCookie.split(";");
postman.setEnvironmentVariable("Cookie", cookies[0]);
var token = postman.getResponseCookie("XSRF-TOKEN")["value"];
postman.setEnvironmentVariable("X-XSRF-TOKEN", token);

By leveraging these features, developers can eliminate manual login steps, avoid environment‑specific Swagger limitations, and achieve seamless API debugging, mocking, and automation.