tests

Original：🇨🇳 Chinese

Translated

Execute and Monitor Testany Tests - Trigger Pipeline Execution, View Results, Check Status

1installs

Sourcetestany-io/testany-agent-skills

Added on2026-02-10

NPX Install

npx skill4agent add testany-io/testany-agent-skills tests

SKILL.md Content (Chinese)

View Translation Comparison →

Execute Testany Tests

Execute Testany test Pipelines and monitor results.

User Input: $ARGUMENTS

Scope of Responsibilities

Trigger Pipeline execution
Monitor execution status
Report execution results
Obtain execution log links

Note: Testany only supports executing Pipelines, not individual Cases directly. To execute a single Case, please first create a Pipeline that includes the Case.

Core Knowledge

Execution Status

Status	Value	Meaning	Final State?
NOT_STARTED	-1	Not started / In queue	No
RUNNING	0	In execution	No
SUCCESS	1	All passed	Yes
FAILURE	2	Has failures	Yes
SKIPPED	3	Skipped (Case only)	Yes
FAIL_AS_EXPECTED	4	Expected failure (Case only)	Yes
CANCELLED	5	Cancelled	Yes
ERROR	99	System error	Yes

Execution Flow

1. testany_execute_pipeline → Trigger execution, get execution_id
2. testany_get_execution → Poll status (every 5-10 seconds)
3. After status becomes final → Report results
4. If there are failures → testany_get_execution_case to get details

Workflow

Confirm Target: Which Pipeline does the user want to execute?
Find Resources: Use
```
testany_list_pipelines
```
to find the target Pipeline
Trigger Execution:
```
testany_execute_pipeline
```
Monitor Status: Poll
```
testany_get_execution
```
until final state
Report Results: Number of passed/failed cases, list of failed cases

Polling Strategy

Initial interval: 5 seconds
Maximum interval: 30 seconds
Timeout limit: Depending on Pipeline complexity, usually 10-30 minutes

Return Format

After task completion, report to the user:

Execution ID (e.g.,
```
Y2K-0001A-0000B
```
)
Execution status (Success/Failure/Timeout)
Number of passed cases
List of failed cases (if any)
Execution duration
Next steps suggestion (e.g., if failed, suggest "Use /debug to troubleshoot the cause of failure")

Reference Documents

For detailed concepts, please refer to:

Core Concepts