Execute a Testany test Pipeline and monitor the results.
User input: $ARGUMENTS
Scope of responsibilities
- Trigger Pipeline execution
- Monitor execution status
- Report execution results
- Get execution log link
Note: Testany only supports executing Pipelines, not executing a single Case directly. To execute a single Case, first create a Pipeline that contains that Case.: Testany only supports executing Pipelines, not executing a single Case directly. To execute a single Case, first create a Pipeline that contains that Case.
Core knowledge
Execution status
| Status | Value | Meaning | Is terminal state |
|---|---|---|---|
| NOT_STARTED | -1 | Not started/queued | No |
| RUNNING | 0 | Executing | 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 | Canceled | Yes |
| ERROR | 99 | System error | Yes |
Execution flow
1. testany_execute_pipeline → 触发执行，获取 execution_id
2. testany_get_execution → 轮询状态（每 5-10 秒）
3. 状态变为终态后 → 汇报结果
4. 如有失败 → testany_get_execution_case 获取详情
Workflow
- Confirm the target: Which Pipeline does the user want to execute?
- Find the resource：
testany_list_pipelinesFind the target Pipeline - Trigger execution：
testany_execute_pipeline - Monitor status: poll
testany_get_executionuntil terminal state - Report results: number of successes/failures, 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 the task is complete, 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-step suggestions (e.g. if failed, suggest "use /debug to troubleshoot the failure reason")
Reference documentation
For detailed concepts, please refer to: