How to Design and Execute Performance Tests for Mini‑Programs with PTS

Mini‑programs are a critical traffic entry in the mobile internet era, and performance bottlenecks can cause white screens or errors that degrade user experience. Before releasing new features, developers must conduct load testing to assess system capacity and configure rate limiting, ensuring the system remains stable under traffic spikes.

Typical Scenarios Requiring Load Testing

Newly developed systems or features need performance baseline data before launch.

Technical tuning or capacity expansion requires performance comparison.

Participating in platform activities (e.g., promotional events) demands a performance assessment.

Four Common Test‑Type Designs

Single‑API Test : Isolate a core business API and identify bottlenecks in its call chain.

Mixed Test : Combine multiple business APIs to evaluate overall concurrent processing capability.

Performance‑Tuning Test : Vary application, JVM, or thread‑pool parameters to find optimal settings.

Long‑Stable Test : Sustain a high concurrency level for extended periods (e.g., 24 h × N days) to detect memory leaks, GC issues, deadlocks, or resource contention; duration can be adjusted based on GC frequency.

Best Practices for Using PTS to Test Mini‑Programs

Unlike testing a self‑hosted website, mini‑program testing requires a valid platform token (e.g., from WeChat or Alipay) that must be refreshed within its validity period.

Method 1 – Programmatically Obtain Token

Develop an API that continuously fetches the platform token during the test.

In the PTS console, create a new scene (e.g., "myAPP").

Under Scene Configuration , add the token‑fetching API as the first request.

Define an output parameter named access_token with source Body: JSON and expression access_token.

Add the actual mini‑program business API (POST method) and reference the token via a body parameter (e.g., input_token).

Configure pressure settings (concurrency, duration) on the Pressure Configuration tab.

Save and start the test.

Method 2 – Manually Record Token

Create a CSV file containing a column of pre‑fetched tokens.

Upload the CSV in the PTS scene under Data Source Management and map the column to a parameter name.

Reference this parameter in the business API body (e.g., token).

Set pressure configuration as needed and launch the test.

Both methods require attention to token expiration; tokens must be refreshed or the test will fail.

Advantages of Using PTS for Mini‑Program Load Testing

Fully self‑developed engine supporting throughput mode and realistic traffic funnel modeling.

Nationwide traffic generation simulating real user distribution.

Diagnostic tools provide stack‑level error details for precise performance issue localization.

Client‑side proxy recording reduces script‑creation effort.

Note: The original article includes promotional pricing information for PTS, which has been omitted to keep the focus on technical guidance.