# Testing Mode

### Switching to Test mode <a href="#switching-to-test-mode" id="switching-to-test-mode"></a>

{% hint style="warning" %}
It is important to note that Test Mode is a Work Manager feature only. When you are working in Builder - even if you accessed it from Test Mode Work Manager - you are working as normal, and any config changes you make impact your Live operations as normal. Please be aware of this if you are working in Builder and testing out changes in Test Mode of Work Manager. There is no feature to access Builder 'in Test Mode'.
{% endhint %}

If your user account is set to allow you to access test data, you can switch your Work Manager environment over to ‘Testing Mode’. You can access Testing Mode by accessing a different url for testing, one with the word '.test' added to the end of the normal domain name. To explain via an example:

**If your Normal Enate URL is**: <https://acmecorp.enate.cloud/yourworkmanagerlink>

**Your Test Mode URL will be**: <https://acmecor&#x70;**.test**.enate.cloud/yourworkmanagerlink>

Once you've type the Testing Mode url into your browser, you'll be met with the standard looking login page for Work Manager. Once you're logged into the testing mode URL, you'll see the standard Testing Mode look to the page that you're used to, with a 'Testing Mode' badge and red colored header bar.

<figure><img src="/files/DqDro1GaSGFH51F1pfkP" alt=""><figcaption></figcaption></figure>

### Test Mode Explanation <a href="#test-mode-explanation" id="test-mode-explanation"></a>

Once you are running in test mode you will only see test data; allowing you to create and run test Work Items through test versions of processes to verify them before setting live, all without affecting live production data.

As a visual reminder, the header bar is set to red when you are in Test mode.

### Defining Different Managers and Members of Queues in Test Mode <a href="#defining-different-managers-and-members-of-queues-in-test-mode" id="defining-different-managers-and-members-of-queues-in-test-mode"></a>

Test mode functionality allows you to set a different manager for a Queue when running in Test mode vs. Live mode.

Example: Consider **Manager 1** who has access to live mode and is responsible for managing two Queues, **Funding** and **Master** **Case** Queue.

<figure><img src="/files/AJ51mgwnlGPDJpkmyPCC" alt=""><figcaption></figcaption></figure>

In Test Mode, the same two Queues can be managed by another user who has Team Lead and Test Mode permission – see below example where **Manager 2** has been set to be in charge of the Queues in Testing Mode.

<figure><img src="/files/YFruq6ncwhkjLnhGirCo" alt=""><figcaption></figcaption></figure>

### Switch Robots between Live and Test <a href="#switch-robots-between-live-and-test" id="switch-robots-between-live-and-test"></a>

It is possible to switch a robot so that it can run in test mode or live mode. Specifically, two new activities have been added to the activity libraries for UiPath, Automation Anywhere and BluePrism (and the standard APIs adjusted so this can be called generically) as follows

* Set Live Mode
* Set Test Mode

These Actions allow you to flip a robot between test and live states. Once a robot has been flipped into Test mode, subsequent activity calls which the robot might make, e.g. ‘Get more work’ and ‘Create Ticket/Case etc.’ take place within that context of Test mode, getting and creating only test work items. The robot should be switched back to Live mode once the process is set to live, so ensure it is then creating live work items.

### Test Contacts - Separate test contacts in the system <a href="#test-contacts-separate-test-contacts-in-the-system" id="test-contacts-separate-test-contacts-in-the-system"></a>

Enate supports the creation of separate Contact records in Test Mode, i.e. any contact records you create in Test mode will be accessible only to Test Mode users (and contacts created in live mode will be accessible only to Live mode users). This helps to ensure that emails from test work items are not accidentally sent to production users, and vice versa.

#### Warning - Do Not Use Production Email Addresses when creating Test Contacts <a href="#warning-do-not-use-production-email-addresses-when-creating-test-contacts" id="warning-do-not-use-production-email-addresses-when-creating-test-contacts"></a>

{% hint style="warning" %}
**IMPORTANT:** Do NOT create Test Contact records using information (specifically email address) for people you will be using in normal production. <br>

**If you create a Contact record while you are in Test mode this will be created as a Test Contact, and ALL emails arriving into the system from that email address will create a Case/Ticket in Test Mode.**&#x20;

This would result in incoming production emails creating work test work items which would not be visible by production users.\
\
If you have created a production Contact record as a Test Contract record in error, you should edit the Test contact by changing the email address, then switch back to normal production mode to create the desired normal Contact record.<br>
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.enate.net/enate-help/work-manager/work-manager-2021.1/test-mode.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.