Considerations for Testing Center

To use Testing Center, consider supported functionality, usage, limitations and allowances, limits, and other issues.

Required Editions

Available in: Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions. Required add-on licenses vary by agent type.

Testing Center Language and Locale Support

Testing Center supports the languages and locales supported on the Salesforce generative AI platform, as described in Einstein Generative AI Supported Languages and Locales.

Testing Center Region Support

Testing Center supports the geo-aware models supported on the Salesforce generative AI platform, as described in Geo-Aware LLM Request Routing on the Einstein Generative AI Platform.

Testing Center and Einstein Requests Usage

As of Summer '26, testing in Agentforce Testing Center is unmetered and doesn't consume Einstein Requests or Flex Credits. Unmetered testing applies to all test types, all agent types, test creation, agent actions from test execution, and result evaluation. Data 360 queries from Agentforce Testing Center are still metered. To learn more about generative AI usage, see Generative AI Billable Usage Types.

Conversation-Level Testing Considerations

  • Context variables are not supported for conversation-level testing.
  • Custom scorers are not supported for conversation-level testing.
  • Generate Test Cases from Knowledge isn't available for conversation-level testing.
  • Conversation-level testing doesn't support Mocked Data or context variables. If either is selected, only text output is available.
  • Voice simulated responses are in English only, regardless of the agent's configured language.
  • In beta, conversation-level testing supports a maximum of 3 concurrent test suites and 20 turns per conversation. You can generate up to 20 test cases from an LLM or upload up to 1,000 test cases from a CSV file.
  • Audio recordings are stored as JSON in org Files. If the file is deleted, audio playback breaks.
  • Conversation generation takes a few minutes. The system generates conversations and audio files in real time.
  • If your agent gets stuck in an authentication or verification loop, specify bypass details in the topic instructions and test objective.
  • To use conversation-level testing with customer verification, set your context variables correctly. Verification codes can't be provided during simulated conversations.
  • Escalation isn't supported. If an escalation is triggered during a conversation-level test, the conversation ends with "User requested transfer to agent."
  • Agentforce Employee Agents aren't supported for conversation-level testing.