Agent Studio Test mode ​

Test mode lets you run your genie in a live, isolated environment during development. You can chat directly with your genie and set up frequently repeated scenarios to test specific responses. The LLM reads your job description, calls skills, and searches the knowledge base. This setup mirrors production behavior.

Test mode allows you to test your genie by asking your own questions or using your own set of established common scenarios. For example, an Authentication issues sample scenario may include the following prompts:

• I can't log in to my account.
• Can you reset my password?
• My user ID isn't recognized.

You can add custom prompts to your scenarios to observe how your genie performs in specific use cases. Refer to Permissions and access governance for information on how to provide testing access to users.

Test mode workflow ​

Test mode relies on the following workflow:

• Skills run against live connected systems: Your Submit Leave Request skill connected to your production HR system submits real leave requests during testing. Temporarily connect the skill to a sandbox environment or be prepared to reverse whatever it creates before running a test that triggers a write operation. Your recipe doesn't know it's being called from a test session.

• Intermediate messages are visible during execution: Intermediate Messages are visible in Test mode and have parity with the messages that are shown in production. Your genie sends intermediate messages with real-time status updates and partial findings as it works through a task before the final response is generated. Intermediate messages are supported in Slack, Microsoft Teams, and Workato GO. For example, if a user asks your genie to summarize the knowledge base, the genie first sends an intermediate message, such as I'll search the knowledge base and provide you with a summary before returning the final two-sentence summary. You can use Test mode to observe intermediate messages in the conversation history panel to verify that your genie is communicating progress accurately and helpfully at each step.

Intermediate messages are automatically enabled on all supported chat interfaces. You can disable intermediate messages for genies at the project level. Refer to Disable intermediate messages for more information.

• Each test session maintains its own conversation context: Your genie remembers what was said earlier in the same test session. This means you can run multiple test scenarios back to back without resetting, but context from the first scenario bleeds into the second and produces misleading results. Use the Reset button between scenarios to clear the conversation history and start fresh.

• Test mode uses your builder identity, not an end-user identity: Skills using Verified User Access to execute with the requesting user's credentials use your credentials as the builder when called in Test mode. Identity-dependent behavior, such as fetching leave balances, reflects your account instead of the end-user. Consider this when you review results.

Test mode connections ​

Your genie executes skills using the connection established in the recipe even when skills use Verified user access. This means that your genie doesn't use an end-user connection configured in the skill when testing.

Complete the following steps if you encounter issues with skill execution during testing:

Create a sample scenario and test messages ​

You can create a custom sample scenario and add your own messages to it. You can add multiple messages to each scenario. Refer to Best practices for testing agents for more examples on how to structure your tests.

Complete the following steps to create a sample scenario and messages:

Edit a sample scenario message ​

Complete the following steps to edit a sample message: