> 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/administration-and-setup/workflow/test-manager.md). # Test Manager The **Test Manager** lets you save reusable **test scenarios** for your workflows and run them together — so you can confirm that a workflow still behaves correctly after you change it. It works for both Standard and Advanced workflows. Open it from **Workflow Dashboard → Test Manager List**.

Test Manager List with test scenarios, status and Run All Tests — The Test Manager List — each saved scenario shows a pass/fail result.

## What a test scenario is A test scenario captures a workflow, a sample input and the **expected outcome**. When you run it, the Test Manager replays the workflow against that input and compares the result to what you expected — turning the row **green** (pass) or **red** (fail). ## Working with scenarios * **Add Test Scenario** — create a new scenario from a workflow and a sample document. * **Run All Tests** — run every scenario at once and see, at a glance, which workflows still pass. * **View Details** — open a scenario to inspect its result.

The details view shows the scenario name and **status**, the **workflow name**, the **run time**, and the **actual** and **extracted data** the run produced — so you can see exactly why a scenario passed or failed. ## Test Manager vs. testing in the builder These are two different things: * **Test Manager** (this page) — *saved, repeatable* scenarios with expected outcomes, run together with **Run All Tests**. Use it for regression testing after changes. * **Testing in the builder** — the inline **Validate** and **Test** controls inside the Advanced Workflow builder, for quick checks while you are building. See [Validation & Testing](/administration-and-setup/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/administration-and-setup/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.