testany-guide
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseTestany 平台参考
Testany Platform Reference
本 skill 提供 Testany 平台的核心概念参考。详细内容见 references/ 目录。
This skill provides core concept references for the Testany platform. For detailed content, see the references/ directory.
核心实体关系
Core Entity Relationships
Case (测试用例)
│
├──► Pipeline (流水线) ──► Execution (执行)
│ │
│ ├──► Plan (定时计划)
│ └──► Gatekeeper (质量门禁)
│
└──► Workspace (工作空间) ──► 权限控制Case (Test Case)
│
├──► Pipeline ──► Execution
│ │
│ ├──► Plan (Scheduled Plan)
│ └──► Gatekeeper (Quality Gate)
│
└──► Workspace ──► Permission Control快速参考
Quick Reference
- 实体定义和可见性规则 → concepts.md
- Executor 配置详解 → executors.md
- Pipeline YAML 语法 → pipeline-yaml.md
- Entity definitions and visibility rules → concepts.md
- Detailed Executor configuration → executors.md
- Pipeline YAML syntax → pipeline-yaml.md
宿主能力适配
Host Capability Adaptation
testany-bot- 如果宿主支持结构化提问工具(如 AskUserQuestion),优先一次性收集缺失信息。
- 如果宿主不支持该工具,则用普通文本在当前对话中提问;低风险字段可给出默认值建议,但必须明确告知用户。
- 如果宿主支持 slash command / router,可推荐相关 workflow 的命令入口。
- 如果宿主不支持 slash command,不要阻塞任务;直接在当前线程继续对应 workflow。
The general version of branches by capability rather than host brand:
testany-bot- If the host supports structured question tools (such as AskUserQuestion), prioritize collecting missing information in one go.
- If the host does not support this tool, ask questions in plain text in the current conversation; for low-risk fields, default value suggestions can be provided, but users must be clearly informed.
- If the host supports slash command / router, recommend the command entry for relevant workflows.
- If the host does not support slash command, do not block the task; continue the corresponding workflow directly in the current thread.
标识符格式
Identifier Format
| 类型 | 格式 | 示例 |
|---|---|---|
| Case Key | 8 位大写十六进制 | |
| Pipeline Key | | |
| Workspace Key | 3 位大写字母数字 | |
| Execution ID | | |
| Type | Format | Example |
|---|---|---|
| Case Key | 8-digit uppercase hexadecimal | |
| Pipeline Key | | |
| Workspace Key | 3-digit uppercase alphanumeric | |
| Execution ID | | |
MCP Schema Resources
MCP Schema Resources
在组装 API payload 前,应先读取对应的 schema resource:
| Resource URI | 用途 |
|---|---|
| Case 创建/更新字段定义 |
| Pipeline YAML 完整 schema |
Before assembling the API payload, read the corresponding schema resource first:
| Resource URI | Purpose |
|---|---|
| Case creation/update field definitions |
| Complete Pipeline YAML schema |