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

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 for installation instructions. Then [MUST] run

aliyun configure set --auto-plugin-install true

to enable automatic plugin installation.

undefined

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.

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

Note: Use

save-pts-scene

instead of

create-pts-scene

. The

--scene

parameter accepts a JSON object directly (not wrapped in a

Scene

field).

Idempotency:

SceneName

may duplicate across scenarios. Do not skip creation or pick a scene based on name alone. After

save-pts-scene

succeeds, record the returned

SceneId

for all later steps. If the command fails or times out with unknown outcome, use

list-pts-scene

together with the user to identify the intended

SceneId

before retrying — avoid blind retries that create extra scenes.

aliyun pts save-pts-scene \
  --scene '{
    "SceneName": "<SCENE_NAME>",
    "RelationList": [
      {
        "RelationName": "serial-link-1",
        "ApiList": [
          {
            "ApiName": "api-1",
            "Url": "<TARGET_URL>",
            "Method": "<HTTP_METHOD>",
            "TimeoutInSecond": 10,
            "RedirectCountLimit": 10,
            "HeaderList": [
              {
                "HeaderName": "User-Agent",
                "HeaderValue": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36"
              }
            ],
            "CheckPointList": [
              {
                "CheckPoint": "",
                "CheckType": "STATUS_CODE",
                "Operator": "eq",
                "ExpectValue": "200"
              }
            ]
          }
        ]
      }
    ],
    "LoadConfig": {
      "TestMode": "concurrency_mode",
      "MaxRunningTime": <DURATION_MINUTES>,
      "AutoStep": false,
      "Configuration": {
        "AllConcurrencyBegin": <CONCURRENCY>,
        "AllConcurrencyLimit": <CONCURRENCY>
      }
    },
    "AdvanceSetting": {
      "LogRate": 1,
      "ConnectionTimeoutInSecond": 5
    }
  }' \
  --user-agent AlibabaCloud-Agent-Skills

• MaxRunningTime

  : Duration in minutes (not seconds), range [1-1440]

• TestMode

  : Use

  concurrency_mode

  for concurrent user testing or

  tps_mode

  for RPS testing

• TimeoutInSecond

  : Request timeout in seconds (recommended: 10)

• RedirectCountLimit

  : Maximum redirects allowed (use

  10

  for normal,

  0

  to disable)

• HeaderList

  : HTTP headers, User-Agent is recommended for better compatibility

• CheckPointList

  : Assertions for response validation (STATUS_CODE, BODY_JSON, etc.)

• AdvanceSetting.LogRate

  : Log sampling rate (1-100)

• AdvanceSetting.ConnectionTimeoutInSecond

  : Connection timeout (recommended: 5)

For complete JSON structure with all fields (POST requests, file parameters, global variables, etc.), see references/pts-scene-json-reference.md

[MUST] Pre-flight Safety Checks — Starting a stress test sends significant traffic to the target system. ALL of the following checks MUST pass before executing

start-pts-scene

:

1. Idempotency guard — Run

   get-pts-scene-running-status --scene-id <SCENE_ID>

   . If the status is

   RUNNING

   or

   SYNCING

   , the test is already in progress — skip the start command and proceed to monitoring. Do NOT start a duplicate test.
2. Retrieve and verify scene configuration — Run

   get-pts-scene --scene-id <SCENE_ID>

   and confirm the response contains a valid

   SceneName

   , at least one

   RelationList

   entry with a non-empty

   Url

   , and a valid

   LoadConfig

   (non-zero

   MaxRunningTime

   and concurrency). If any field is missing or empty, abort and notify the user.
3. Display test summary and require explicit user confirmation — Present the following to the user and wait for explicit approval (e.g., "yes" / "确认"):
   • Target URL(s)
   • Concurrency level
   • Test duration
   • Test mode (concurrency / TPS)
   Do NOT proceed without the user's explicit "go-ahead" confirmation.

undefined

Idempotency:

SceneName

may duplicate across JMeter scenarios. Do not dedupe by name. After

save-open-jmeter-scene

succeeds, record the returned

SceneId

. On uncertain failure, use

list-open-jmeter-scenes

with the user to disambiguate before retrying.

aliyun pts save-open-jmeter-scene \
  --open-jmeter-scene '{
    "SceneName": "<SCENE_NAME>",
    "TestFile": "<JMX_FILENAME>",
    "Duration": <DURATION>,
    "Concurrency": <CONCURRENCY>,
    "Mode": "CONCURRENCY"
  }' \
  --user-agent AlibabaCloud-Agent-Skills

[MUST] Pre-flight Safety Checks — Starting a JMeter stress test sends significant traffic to the target system. ALL of the following checks MUST pass before executing

start-testing-jmeter-scene

:

1. Idempotency guard — Run

   get-open-jmeter-scene --scene-id <SCENE_ID>

   and check the scene status. If the test is already running, skip the start command and proceed to monitoring. Do NOT start a duplicate test.
2. Verify scene configuration — From the same response, confirm it contains a valid

   SceneName

   , a non-empty

   TestFile

   , and non-zero

   Duration

   and

   Concurrency

   . If any field is missing or empty, abort and notify the user.
3. Display test summary and require explicit user confirmation — Present the following to the user and wait for explicit approval (e.g., "yes" / "确认"):
   • Scene name and JMX file
   • Concurrency level
   • Test duration
   Do NOT proceed without the user's explicit "go-ahead" confirmation.

undefined

IMPORTANT:

start-pts-scene

may return

Success: true

even when the stress test fails to actually launch (e.g., due to target site protection or missing configuration). Always verify actual execution status.

undefined

[MUST] Pre-delete Safety Checks — Before deleting any scenario, ALL of the following checks MUST pass:

1. Idempotency guard — Using the target

   SceneId

   (not name), verify it still exists (e.g.

   list-pts-scene

   /

   list-open-jmeter-scenes

   or

   get-*

   ). If that

   SceneId

   is absent, treat deletion as already done and skip the delete command.
2. Check if the scenario is currently running — Run

   get-pts-scene-running-status --scene-id <SCENE_ID>

   (PTS) or check JMeter scene status. If the scenario status is

   RUNNING

   or

   SYNCING

   , you MUST stop it first using

   stop-pts-scene

   /

   stop-testing-jmeter-scene

   and wait for it to fully stop before deleting. Do NOT delete a running scenario.
3. Require explicit user confirmation — Display the scene name and ID to the user and ask for explicit deletion confirmation (e.g., "yes" / "确认删除"). Do NOT proceed without the user's explicit approval.

undefined

1. Use complete scene configuration - Always include

   TimeoutInSecond

   ,

   HeaderList

   (with User-Agent),

   CheckPointList

   , and

   AdvanceSetting

   for reliable test execution
2. Always confirm parameters - Verify target URLs, concurrency settings, and duration with the user before execution
3. Start with low concurrency - Begin with low concurrency and gradually increase to identify performance thresholds
4. Verify actual execution - Don't trust

   Success: true

   from

   start-pts-scene

   ; always check

   get-pts-scene-running-data

   with

   --plan-id

5. Use debug mode first - For PTS scenarios, use

   start-debug-pts-scene

   to validate configuration before full tests
6. Monitor during tests - Regularly check running status during stress tests
7. Review reports thoroughly - Analyze response times, error rates, and throughput in reports
8. Clean up after testing - Delete test scenarios to avoid unnecessary costs
9. Use appropriate test duration - Longer tests provide more accurate results but consume more resources
10. Include warmup period - Allow time for systems to warm up before measuring peak performance