Important note: This feature is available in Preview for select customers. To join the Preview program, please contact your Talkdesk representative.
Overview
Test mode is a feature in the Talkdesk Studio™ editor that runs a single-component configuration test on a node, allowing Admins to test nodes without generating a real interaction.
Test mode supports the following nodes:
- Calendar Based Rules.
- Conditional Statement.
- Time Based Rules.
- Traffic Splitter.
Table of Contents
- Understanding Test Mode
- Accessing Test Mode
- Testing Calendar Based Rules
- Testing Conditional Statement
- Testing Time Based Rules
- Testing Traffic Splitter
- Resources
Understanding Test Mode
Test mode runs a "direct test" that evaluates the node configuration against the test inputs that Admins provide. Each test uses the following elements:
- Dynamic values: Some node fields are configured with variables. Admins enter content for each variable before running the test.
- Interaction context: Information passed to the node, such as a time zone, a date, or a time, to run against the configuration.
- Special testing scenarios: Some scenarios cannot be replicated naturally, so Admins can force one. Selecting "Force component failure" makes the node use its error handling behavior.
- Test results: Each result shows whether the test was performed, which exit was taken, and the next node in the flow. Results also list any variable outputs generated.
- Traffic Splitter results differ: they show the distribution of executions across exits.
Accessing Test Mode
To access Test mode, complete the following steps:
- Open the flow in the Studio editor [1].
- Click Test on the right-hand side of the header [2].
- Select the node to test (the ones that are available to be tested will have a dotted contour) [3].
- Open its Test tab and test without generating a real interaction [4].
Testing Calendar Based Rules
- Calendar Based Rules testing lets Admins simulate a specific day and time zone and check the input against the node configuration. This node requires no dynamic values. To run the test, enter the following interaction context:
- Timezone: Select the time zone to simulate.
- Date: Select a day to check which calendar rule it falls into.
After entering the context, click Run test.
The test result shows whether the input matched a configured exit, the name of the exit taken, and the next node in the flow. In the example below, the date matched an "Oct 1" calendar range. The result shows the exit "go time" and the next node "time".
Testing Conditional Statement
Conditional Statement testing lets Admins check the node against its configured conditions. This node requires dynamic values but no interaction context. In the “Dynamic values” section, enter content for each listed variable, and then click Run test.
The test result shows the exit taken, the next node, and the variable outputs. If the input does not meet any condition, the result displays a "No condition matched" warning and the "No Match" exit. Admins should then verify whether this is the intended behavior.
Testing Time Based Rules
Time Based Rules testing follows the same structure as Calendar Based Rules, with one additional input. To run the test, enter the following interaction context:
- Timezone: Select the time zone to simulate.
- Date: Select a day to check which time rule it falls into.
- Time: Enter a time to check which time rule it falls into.
After entering the context, click Run test.
The test result shows the following information:
- Whether the test was performed successfully.
- Whether the input matched a configured exit.
- The name of the exit taken.
- The next node the flow is expected to follow after the test input.
Testing Traffic Splitter
Traffic Splitter testing lets Admins test the distribution algorithm for a chosen number of executions, up to 100. This node requires no dynamic values. To run the test, enter the following interaction context:
- Number of executions: Enter the number of executions the algorithm distributes. This field is required.
Admins can also select a special testing scenario: "No special testing scenario applied" or "Force component failure". The second option makes the node use its error handling behavior.
After the test runs, the result shows whether the test was performed and the distribution of executions across exits. Each exit displays a percentage, a count, and the next node. In the example below, 10 executions split evenly, with about 50.0% (five executions) going to each of two exits.
Resources
For more information on Studio and Studio nodes, please visit our Talkdesk Studio documentation here.