Apipost Test Platform Integration
This article explains how to integrate the Apipost test platform with Zadig, execute automated tests, analyze test reports, and leverage Zadig's environment capabilities to shift testing left, empowering other roles to participate in quality assurance, thereby effectively reducing the cost of identifying and fixing issues.
# Apipost Integration
# Step 1: Configure Continuous Integration in Apipost
Access Apipost Automated Test → Continuous Integration, create a new configuration and copy the Apipost CLI command.


# Step 2: Configure Node.js in Zadig
Zadig system administrators can access system settings → Integration Management → Package Management, and add a new package.

Configuration instructions:
- Name: node
- Version: 20.5.1
- Bin Path: $HOME/node/bin
- Package address: https://nodejs.org/dist/v20.5.1/node-v20.5.1-linux-x64.tar.xz
- The installation script is as follows:
mkdir -p $HOME/node
tar -C $HOME/node -xJf ${FILEPATH} --strip-components=1
npm config --global set registry https://registry.npmmirror.com/
2
3
# Step 3: Configure Testing in Zadig
Enter the project's test module, click Create Test to complete the test configuration.


Configuration instructions:
- Dependent Software Package: Select node 20.5.1
- Test script: Apipost Continuous Integration CLI, plus --out-file=report --out-dir=$WORKSPACE. The example is as follows:
#!/bin/bash
set -ex
npm install -g apipost-cli-pro
apipost run "https://open.apipost.net/open/ci/automated_testing?ci_id=MjExNTcwODk1MTIxNDQwNzY4OjEzNDE0MDY0NDExNDMwOTEyOjEzNDIyNTg2MzYwNTQ5Mzky&token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VyX2lkIjoyMTE1NzA2MzY0MjkzNTI5NjAsImlzcyI6ImFwaXBvc3QiLCJleHAiOjE3MjIwNjg0MjJ9.CLXvIwehOHAkx07NcRPAXwPsn6zSkorwrW4O1f3zq9A" -r html --out-dir=$WORKSPACE --out-file=report
2
3
4
5
- Html Report File Path:
$WORKSPACE/report.html
Notification
Refer to Notification Configuration.
# Automated Test Execution
Executing the Zadig test will automatically trigger the Apipost automated test. Once the Zadig test is successfully executed, the execution status will be notified in the IM. The example below is for Feishu.

# Test Report Analysis
Click the test results link in the IM notification to view and analyze the test report.

# Test Left Shift
Configure workflows to orchestrate build, deployment (development environment), and testing tasks. Refer to Workflows.

After completing the feature development, submit a code change PR, and select the PR change to execute the workflow to deploy the development environment and run automated tests. This allows quality issues to be identified and fixed early in the development process.




