> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/chinese/guan-li-yu-she-zhi/workflow/test-manager.md). # 测试管理器 **测试管理器**允许您为工作流保存可重复使用的**测试场景**并批量运行，以便在更改工作流后确认其行为仍然正确。它适用于标准工作流和高级工作流。从 **Workflow Dashboard → Test Manager List** 打开。

测试管理器列表，显示测试场景、状态和 Run All Tests — 测试管理器列表 — 每个已保存的场景都会显示通过或失败结果。

## 什么是测试场景测试场景包含一个工作流、一个示例输入和**预期结果**。运行场景时，测试管理器会使用该输入重新执行工作流，并将结果与预期结果进行比较 — 通过时将该行标为**绿色**，失败时标为**红色**。 ## 使用测试场景 * **Add Test Scenario** — 根据工作流和示例文档创建新的场景。 * **Run All Tests** — 一次运行所有场景，一目了然地查看哪些工作流仍能通过测试。 * **View Details** — 打开场景并检查其结果。

工作流测试场景详情，包含状态、运行时间和数据 — 场景详情 — 名称、状态、运行时间，以及本次运行生成的实际数据与提取数据。

详情视图会显示场景名称和**状态**、**工作流名称**、**运行时间**，以及本次运行生成的**实际数据**和**提取数据** — 让您准确了解场景通过或失败的原因。 ## 测试管理器与构建器中的测试这是两种不同的功能： * **Test Manager**（本页）— 使用**Run All Tests**批量运行具有预期结果的\_已保存、可重复执行\_场景。用于更改后的回归测试。 * **构建器中的测试** — Advanced Workflow 构建器中的内联 **Validate** 和 **Test** 控件，供您在构建时快速检查。请参阅[验证与测试](/chinese/guan-li-yu-she-zhi/workflow/advanced-workflow-builder/validation-and-testing.md)。 --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.docbits.com/chinese/guan-li-yu-she-zhi/workflow/test-manager.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.