Mocking - Cognigy Documentation

Documentation Index

Fetch the complete documentation index at: /llms.txt

Use this file to discover all available pages before exploring further.

Added in 2026.10

Mocking lets you change the behavior of a Node by replacing its logic with mock code without changing the original Node settings. This approach allows you to keep the original Flow logic and mock Node behaviors to test specific Flow conditions in the Simulator, the Interaction Panel, and Endpoints without reconfiguring Nodes.

Key Benefits

• Testing Flexibility. Replace any Node’s output or function without changing Flow paths or production logic. To change the Node’s behavior, you can just activate mocking and add mock code.
• Cost Savings. Run simulations with lower costs or less time by mocking data to avoid sending HTTP or LLM requests.
• Consistent Testing Interactions. Control interactions for AI Agent testing by mocking LLM responses with deterministic data.

Restrictions

• If you activate mocking for a Node that has child Nodes, for example, the Then and Else Nodes of an If Node, the child Nodes aren’t executed. However, you can use mocking on child Nodes.

How Mocking Works

Mocking provides the Mock Code field in every Node’s settings in the Node editor. This field supports JavaScript code to access the Input, Context, and Profile objects, and api.say function. The mock code entirely overrides the configured Node’s execution logic at run-time. With the Mock Code field, you can mock:

• The AI Agent output, for example, api.say("Are there any requirements for the drilling machine?").
• User input and data, and third-party requests, by storing data in:
  • the Input object, for example, input.text = "I would like to buy a drilling machine".
  • the Context object, for example, context.selectedProduct = "Drilling machine".
  • the Profile object, for example, profile.name = "John Doe".

If you activate mocking for Nodes that control Flow paths, for example, the If and Go To Nodes, the Flow execution is affected. This approach can lead to tests and simulations that don’t reflect your use case, for example, one of the branches of the If Node can’t be executed.

How to Use Mocking

To use mocking, you need to activate it at both levels:

• the Node level. Enter the mock code to replace the Node’s logic.
• the interface level. The mock code replaces the Node’s logic only in the interface you activate mocking for. You can use the following interfaces to run tests with mock code: - Interaction Panel
  • Simulator
  • individual Endpoints

By selecting the interface for mocking, you can limit where mocking applies. For example, you can have interactions using the original Flow logic through one Endpoint and test conversations with the mock code logic through another Endpoint or in the Simulator.

Activate Mocking

At the Node Level

1. Go to Build > Flows, select the Flow you want to test.
2. Right-click the Node you want to mock a behavior for and select Enable Mocking. The icon appears next to the Node to indicate that the Node logic is replaced by the mock code.
3. Click the Node. The Node editor opens.
4. In the Mocking section, enter the mock code in the Mock Code field, for example, api.say("Are there any requirements for the drilling machine?"). Save the Node.

At the Interface Level

• Interaction Panel
• Simulator
• Endpoints

1. In the upper-right corner, click to open the Interaction Panel.
2. Click the Settings tab and toggle on the Enable Mocking setting in the Advanced section.

Now, you can run the Flow with the mock code in the Interaction Panel, both in chat and simulation modes.

1. In Test > Simulator, select the scenario you want to run with the mock code.

2. In the Start Simulation panel, toggle on the Enable Mocking setting.

3. In Deploy > Endpoints, select the Endpoint you want to test with the mock code.

4. In the Advanced Settings section of the Test Endpoint panel, toggle on the Enable Mocking setting.

Deactivate Mocking

To fully deactivate mocking, deactivate it at Node and interface levels. However, you can selectively deactivate mocking:

• Deactivate mocking only at the Node level — switches only the Node’s execution logic back to the original Node settings. If you have other Nodes with active mocking, their mock code is executed instead of the original Node settings.
• Deactivate mocking only at the interface level — switches the Node execution logic of all Nodes with mock code back to the original Node settings for that interface. If you have active mocking for other interfaces, the mock code is executed instead of the original Node settings.

This approach provides flexibility to easily switch between mocked and original behavior.

Deactivate at the Node Level

1. Go to Build > Flows, select the relevant Flow.
2. Right-click the Node you want to deactivate mocking for and select Disable Mocking.

Deactivate at the Interface Level

• Interaction Panel
• Simulator
• Endpoints

1. In the upper-right corner, click to open the Interaction Panel.

2. Click the Settings tab and toggle off the Enable Mocking setting in the Advanced section.

3. In Test > Simulator, select the scenario you want to run with the mock code.

4. In the Advanced section of the Start Simulation panel, toggle off the Enable Mocking setting.

5. In Deploy > Endpoints, select the Endpoint you want to test with the mock code.

6. In the Advanced Settings section of the Test Endpoint panel, toggle off the Enable Mocking setting.

Examples

The following examples show how to use mock code in different cases.

Mock a User Response To test how your AI Agent performs when it receives a predefined response from the user to a Question Node, you can mock the response. Consider that you have a Question Node that stores the user’s response in input.result. Follow these steps:

1. Right-click the Question Node you want to mock a behavior for and select Enable Mocking.
2. Open the Node editor and enter the code to mock the user’s response, for example:

input.result = "I would like to order a drilling machine";

Mock an AI Agent Response To test a predefined response instead of an LLM-generated response, for example, from an LLM Prompt Node, follow these steps:

1. Right-click the LLM Prompt Node you want to mock a behavior for and select Enable Mocking.
2. Open the Node editor and enter the code to mock the AI Agent’s response, for example:

api.say("Are there any requirements for the drilling machine?");

Replace Costly Requests Your Flow may contain HTTP or LLM requests that may incur costs or take a long time to complete. These requests could cause issues if you test your AI Agent with frequent simulations. To avoid these issues, you can mock a request during the simulations, for example, in an HTTP Request Node. Consider an HTTP Request Node that retrieves information about a movie from the OMDB API database and stores it in the Input object under input.movie. You can mock the request of the HTTP Request Node with a predefined response. To do so, follow these steps:

1. Right-click the HTTP Request Node you want to mock a behavior for and select Enable Mocking.
2. Open the Node editor and enter the mock output in the Mock Code field, for example:

input.movie = {
     "Title": "Inception",
     "Year": "2010",
     "Rated": "PG-13",
     "Released": "16 Jul 2010",
     "Runtime": "148 min",
     "Genre": "Action, Adventure, Sci-Fi",
     "Director": "Christopher Nolan",
     "Writer": "Christopher Nolan",
     "Actors": "Leonardo DiCaprio, Joseph Gordon-Levitt, Elliot Page",
     "Plot": "A thief who steals corporate secrets through the use of dream-sharing technology is given the inverse task of planting an idea into the mind of a CEO.",
     "Language": "English, Japanese, French",
     "Country": "USA, UK",
     "Awards": "Won 4 Oscars. Another 152 wins & 218 nominations."
};

More Information

• Simulator
• Interaction Panel
• Endpoints