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

# Test suite

> Save conversations as test cases and re-run them to check for regressions.

The **Test suite** lets you save real conversations as test cases and re-run them against Draft or Sandbox to check for behavioral drift. Each case captures the full conversation — user messages, agent replies, and tool calls — so you can verify the agent still handles the scenario correctly after changes.

## Create a test case from a conversation

<Steps>
  <Step title="Open a conversation in Conversation Review">
    Go to **Analytics > Conversations** and select a conversation. In the side panel, click the **Add test** button.

    <img src="https://mintcdn.com/polyai/zdYy6ORmlm_2Hesc/images/analytics/test-suite-add-from-review.png?fit=max&auto=format&n=zdYy6ORmlm_2Hesc&q=85&s=96b0692a39e34490c8a9a74fbfa27283" alt="Add test from Conversation Review" width="2998" height="1288" data-path="images/analytics/test-suite-add-from-review.png" />
  </Step>

  <Step title="Name the test case">
    In the **Create test case** modal, give the case a descriptive name (for example, "Sunday Opening Test") and click **Create**.

    <img src="https://mintcdn.com/polyai/zdYy6ORmlm_2Hesc/images/analytics/test-suite-create-modal.png?fit=max&auto=format&n=zdYy6ORmlm_2Hesc&q=85&s=18d39317c6762ee74bbd76ca7e936ce6" alt="Create test case modal" width="1828" height="1096" data-path="images/analytics/test-suite-create-modal.png" />
  </Step>

  <Step title="Review the test case">
    The test case opens with the full conversation transcript. Edit assertions and user input to define what counts as a successful run.

    <img src="https://mintcdn.com/polyai/zdYy6ORmlm_2Hesc/images/analytics/test-suite-case-view.png?fit=max&auto=format&n=zdYy6ORmlm_2Hesc&q=85&s=c50b1b39f78307aea9ad946f92758a46" alt="Test case view" width="2980" height="1242" data-path="images/analytics/test-suite-case-view.png" />
  </Step>
</Steps>

## Edit test case parameters

Each test case stores the function call values from the original conversation. You can edit these to test variations of the same scenario without creating a new case.

1. Open the test case from **Test suite**.
2. Select the parameters you want to modify.
3. Adjust values to simulate a different scenario — for example, change a date, customer ID, or location.
4. Save the case.

<Tip>
  Editing parameters is useful for testing edge cases. For example, duplicate a booking test case and change the party size to test large-group handling.
</Tip>

## Best practices

* **Save tests from real conversations** — cases from [Conversation Review](/analytics/conversations/review) capture real-world scenarios your agent has already encountered.
* **Name cases descriptively** — use names that describe the scenario, not the expected outcome (for example, "Sunday Opening Test" rather than "Test 1").
* **Cover edge cases** — duplicate a case and tweak parameters to test boundary conditions without re-recording a conversation.
