/alibabacloud-pts-ops

name: alibabacloud-pts-ops
description: |
  Alibaba Cloud PTS (Performance Testing Service) scenario-based skill for creating and managing stress testing scenarios.
  Supports both PTS native HTTP/HTTPS stress testing and JMeter-based stress testing.
  Triggers: "PTS", "压测", "性能测试", "stress testing", "performance testing", "JMeter", "load testing", "创建压测场景"
required_permissions:
  - pts:CreatePtsScene
  - pts:GetPtsScene
  - pts:ListPtsScene
  - pts:StartPtsScene
  - pts:StopPtsScene
  - pts:DeletePtsScene
  - pts:StartDebugPtsScene
  - pts:GetPtsReportDetails
  - pts:GetPtsSceneBaseLine
  - pts:GetPtsSceneRunningData
  - pts:GetPtsSceneRunningStatus
  - pts:SaveOpenJMeterScene
  - pts:GetOpenJMeterScene
  - pts:ListOpenJMeterScenes
  - pts:StartTestingJMeterScene
  - pts:StopTestingJMeterScene
  - pts:RemoveOpenJMeterScene
  - pts:GetJMeterReportDetails

Alibaba Cloud PTS Stress Testing Scenario Management

This skill enables you to create and manage stress testing scenarios using Alibaba Cloud PTS (Performance Testing Service). It supports both PTS native HTTP/HTTPS stress testing and JMeter-based stress testing.

Scenario Description

PTS (Performance Testing Service) is Alibaba Cloud's fully managed performance testing platform that helps you validate the performance, capacity, and stability of your applications. This skill covers:

1. **PTS Native Stress Testing** - Create HTTP/HTTPS stress testing scenarios with configurable APIs, serial links, and load models 2. **JMeter Stress Testing** - Upload and run JMeter scripts with distributed load generation

Architecture

User → Aliyun CLI → PTS Service → Target Application
                         ↓
                   Stress Testing Report

Pre-check

> **Pre-check: Aliyun CLI >= 3.3.1 required** > Run `aliyun version` to verify >= 3.3.1. If not installed or version too low, > see [references/cli-installation-guide.md](references/cli-installation-guide.md) for installation instructions. > Then **[MUST]** run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation.

# Verify CLI version
aliyun version

# Enable auto plugin installation
aliyun configure set --auto-plugin-install true

Timeout Settings

All CLI commands should include timeout parameters to avoid hanging:

# Recommended timeout settings for PTS operations
--read-timeout 60 --connect-timeout 10

• **read-timeout**: 60 seconds (stress testing operations may take longer)
• **connect-timeout**: 10 seconds

Environment Variables

No additional environment variables required beyond CLI authentication.

Parameter Confirmation

> **IMPORTANT: Parameter Confirmation** — Before executing any command or API call, > ALL user-customizable parameters (e.g., RegionId, scene names, target URLs, > concurrency, duration, JMX files, etc.) MUST be confirmed with the user. > Do NOT assume or use default values without explicit user approval.

User-Customizable Parameters

| Parameter Name | Required | Description | Default Value | |---------------|----------|-------------|---------------| | RegionId | No | Region for PTS service | cn-hangzhou | | Scene Name | Yes | Name of the stress testing scenario | - | | Target URL | Yes | URL to stress test | - | | HTTP Method | Yes | GET, POST, PUT, DELETE, etc. | GET | | Concurrency | Yes | Number of concurrent users | - | | Duration | Yes | Test duration in seconds | - | | JMX File | Yes (JMeter) | Path to JMeter script file | - | | Mode | No | CONCURRENCY or TPS | CONCURRENCY |

Authentication

This skill relies on the Aliyun CLI's default credential chain. Ensure your CLI is already authenticated before use.

Verify current authentication:

aliyun configure get

If CLI is not yet configured, see [references/cli-installation-guide.md](references/cli-installation-guide.md) for setup instructions.

RAM Policy

Users must have appropriate PTS permissions. See [references/ram-policies.md](references/ram-policies.md) for detailed policies.

Idempotency

PTS APIs do not support `ClientToken`-based idempotency. **Scene names are not unique** — multiple PTS or JMeter scenarios may share the same `SceneName`. Never treat “same name” as one resource; always use **`SceneId`** (returned by the API) as the stable identifier.

To prevent duplicate resources or unintended side-effects when retrying after timeouts or errors, **always** use the **check-then-act** pattern before every write operation:

| Operation | Check Before Acting | If Already Exists / Running | |-----------|--------------------|-----------------------------| | **Create PTS scene** (`save-pts-scene`) | Do **not** dedupe by name. After success, record `SceneId`. | If the prior call outcome is unknown, use `list-pts-scene` **with the user** to disambiguate before retrying; do **not** blindly retry save (each retry may create another scene). | | **Create JMeter scene** (`save-open-jmeter-scene`) | Same as PTS — names may duplicate; use `SceneId` only. | Same pattern with `list-open-jmeter-scenes` + user disambiguation before retry. | | **Start PTS test** (`start-pts-scene`) | `get-pts-scene-running-status` — check status | If `RUNNING` or `SYNCING`, skip; do NOT start again | | **Start JMeter test** (`start-testing-jmeter-scene`) | `get-open-jmeter-scene` — check status | If already running, skip; do NOT start again | | **Delete PTS scene** (`delete-pts-scene`) | Confirm target **`SceneId`** still exists (e.g. `list-pts-scene` / `get-pts-scene`) | If that `SceneId` is gone, treat as success (already deleted) | | **Delete JMeter scene** (`remove-open-jmeter-scene`) | Confirm target **`SceneId`** still exists | If that `SceneId` is gone, treat as success (already deleted) |

Core Workflow

> **IMPORTANT: Parameter Confirmation** — Before executing any command or API call, > ALL user-customizable parameters (e.g., RegionId, scene names, target URLs, > concurrency, duration, etc.) MU