> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/command-centre/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/testing-a-workflow-version.md).
# Testing a Workflow Version
Testing a workflow is the recommended way to verify its functionality, appearance, process flow, and the actions it triggers in Command Centre. Every workflow should be tested before publishing. Once published, a workflow cannot be set to testing again.
The testing function is also useful when changes to a published workflow are required. By using the Testing status on a new workflow version, you're able to test changes without interrupting the active and published workflow instance.
{% hint style="info" %}
Only one workflow version can be tested at a time.
{% endhint %}
## How to test workflows?
To set a workflow version for testing, use one of the methods below.
{% hint style="success" %}
You can edit the workflow in testing mode. Remember to save any changes you apply.
{% endhint %}
{% stepper %}
{% step %}
### Go to the Workflow Builder module
The module displays the list of available workflows.
{% endstep %}
{% step %}
### Select the workflow you want to test
This opens a workflow side panel displaying different workflow versions.
{% endstep %}
{% step %}
### Set the status of a selected workflow version to Testing
In the sidebar, in the **Actions** column, click the **three-dot** menu and select **Test**. This changes the status of the selected workflow version to Testing and makes it available for testing in the [Workflow Management module.](#testing-in-workflow-management-module)
{% endstep %}
{% endstepper %}
You can also set the workflow to testing directly from the workflow editing screen in the workflow builder.
{% stepper %}
{% step %}
### Go to the Workflow Builder module
The module displays a list of workflows. In Workflow Builder, either open an [existing workflow for editing](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/editing-a-workflow-version.md) or [create a new one.](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/creating-a-new-workflow.md)
{% endstep %}
{% step %}
### In the Workflow Editing View, Click **Test**
Open the workflow for editing and click **Test** in the top bar. This changes the status of the selected workflow version to **Testing** and makes it available for testing in the [Workflow Management module](#testing-in-workflow-management-module).
{% endstep %}
{% step %}
### Confirm in the Pop-Up
After clicking Test, confirm that you want to set the workflow to testing mode. The workflow version is now available for [testing in the Workflow Management](#testing-in-workflow-management-module) module.
{% endstep %}
{% endstepper %}
### **Testing in Workflow Management Module**
{% stepper %}
{% step %}
### Go to the Workflow Management Module
The module contains the list of all workflows along with their statuses.
{% endstep %}
{% step %}
### Select the workflow you set to testing mode
Click on the workflow to access options for managing [visibility post-publication](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/publishing-a-workflow-version.md#how-to-control-published-workflow-visibility) and executing test versions.
{% endstep %}
{% step %}
### Click the **Test Version** Tab
Click the **Run Test Version button** to view the workflow execution. After testing, you are returned to the Make a Request dashboard. Repeat the testing as needed by revisiting the Workflow Management module.
{% hint style="warning" %}
All actions executed by the workflow in the Command Centre during testing will affect the Command Centre environment integrated with AccessNow.
{% endhint %}
{% endstep %}
{% step %}
### Create a New Test Request
To create a new test request, follow the workflow being tested. It should send notifications, create approval tasks, and perform Command Centre actions. Start by triggering the requester part of the workflow and verify that it behaves as expected.
{% endstep %}
{% step %}
### Validate the Approver Experience
To test the parts of the workflow that are not visible to the requester, such as approval, you must use an approver account or ask a privileged approver for help. Then check that the approver part of the workflow is also working correctly.
This task separation is due to the fact that no user can approve their own requests, even if they are just test requests.
After finalizing your workflow, you can move forward with [publishing](/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/publishing-a-workflow-version.md).
{% endstep %}
{% endstepper %}
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.security.gallagher.com/command-centre/accessnow-user-guide/workflow-creation/creating-and-managing-workflows/workflow-management/testing-a-workflow-version.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.