Agent Testing

Summary

In the side menu, open Agents and select an agent in the list. On a computer, the test chat is on the right of the settings form. On a phone, open Testing using the triangle button above the form.

Check answers before publication and after changing instructions, the model, knowledge base, MCP servers, variables, or allowed functions. The test chat uses the saved draft; you do not need to publish it for testing. If the agent has not been created yet, first finish manual creation.

How the test window works

The agent testing panel opens directly in the agent form, so there is no need to switch to a separate section.

If a variant created during auto-training is being tested, the test window opens that exact variant. Media from the test dialog opens over the cabinet: images in the viewer and videos in the player.

In edit mode, the agent form saves the draft automatically. The save indicator is in the agent form header, not inside the chat. It shows whether changes are saving, saved, or have failed; the hint shows the last saved time. You do not need to click Save for test separately in this form.

Until a test dialog has been created or selected, the chat title shows the name of the agent being tested. The list in the panel contains only that agent's test dialogs, so tests from different agents do not mix.

Test the agent before publication

1. Open the required agent's test chat as described above.
2. Wait for successful draft autosave in the form header.
3. Send a request that resembles a real customer question.
4. Check the answer text, knowledge base materials used, tool calls, and variable substitution.
5. Repeat the check for important edge cases: an incomplete question, missing data, and a request that should be handed to an operator.
6. Return to the settings, fix the issues you found, and wait for the draft to save again.
7. When the result is satisfactory, publish the agent. Real dialogs start using the changes only after publication.

A response test does not check whether the agent will be assigned to a website visitor or a user in another channel. Check Autostart, channels, and activity separately before launch.

In a test response, check not only the final text but also the sources: which knowledge was found, whether tools were called, whether the agent asked for unnecessary secrets, and whether it claimed an action that did not actually complete.

If the test does not run

• check the draft autosave indicator and last saved time;
• check that the testing panel has loaded;
• check the selected model;
• if an error above the form says MCP servers, sets, or metrics failed to load, select Retry and wait for the data;
• check MCP servers if the answer depends on the tools;
• check your balance and available functions.