---
title: "Using Testing Simulation in the Debugger"
slug: "using-the-testing-simulation-in-the-debugger"
description: "Use Simulation data to test Flow Steps and scenarios without executing them in production, the Debugger, or Unit Tests."
updated: 2026-06-26T18:54:15Z
published: 2026-06-26T18:54:15Z
canonical: "documentation.decisions.com/using-the-testing-simulation-in-the-debugger"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Using Testing Simulation in the Debugger

## Overview

The **Simulation** function can be found in the **Testing and Simulation** section of the Steps properties. During Simulation, the Step is not executed; the step will return data specified in the **Simulation** **Data** field without being executed. Specify if this simulated data will run in production, the Debugger, or Unit Tests. This is helpful when a user needs to simulate events, such as specific outputs or values that aren't easily replicated. This allows one to test different scenarios without needing the actual data in the source.

---

## Example

This example shows how to utilize this simulated function on a **Fetch Entity** step.

This technique can be applied to any step needed to simulate data. The Fetch Entity and Show Pop-Up steps are used to demonstrate using the testing and simulation features.

1. From a Designer Folder and select [**CREATE FLOW**](/version-10/docs/create-flows).
2. Add a [**Fetch Entities**](https://documentation.decisions.com/step-library/docs/fetch-entities-step) step from the **DATABASE** category in the **Toolbox** panel
3. Connect both **paths** to the **End** step.
4. Select the step to open its **Properties** tab; under the **Type Name** drop-down, search for a select **Account**. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779110895368.png)
5. Navigate to and expand the **Testing and Simulation** section. Here, decide if the simulated data will affect production, the Debugger, or Unit Tests. For this example, **InDebugger** is selected.
6. Defining **Use Simulation Behavior** will display an S icon within a purple circle on the step that uses the behavior.

| **InDebugger** | This only occurs when running the Flow via the Debugger. |
| --- | --- |
| **InProduction** | When the Flow runs, the simulated behavior will be applied when the Flow is run outside of the Debugger (i.e.: Run Flow, calling Flow via API, etc.) |
| **InUnitTests** | The simulated data will be applied when running a unit test which is different from running this through the Debugger itself. |
7. In the **Simulation Selected Path** drop-down, select the "Results" path.
8. For **SimulationEntity Result**, set the data Input to **Constant**.
9. Select **Add** to configure the dummy data for the Debugger.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779111065932.png)
10. A new window will open. **PICK** an **Account** from the left. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779111118123.png)
11. From the **FAVORITE STEPS** category in the Toolbox tab, add a **Show Pop-up** step to the **Results** path.
12. From the **INPUTS** of the Show Pop-Up step, Select From Flow map **EntityResults.All EmailAddress.First** to Subject. For Message, set it to **Ignore**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779111793035.png)

---

## Debug

1. From the Flow Designer, select the **Debug** link from the top **Action** bar.
2. Select START DEBUGGING.  
  
The Flow will run, and the Account defined as the Simulation will display in the Pop-Up.  
This demonstrates a successfully simulated result using the Testing and Simulation settings of the Fetch Entities step.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/image-1779111824485.png)