# Validate case workflows with test cases

Supported in: This document explains how to create and use a test case, which is an
isolated copy of a regular case. Any actions you perform on entities in a
test case don't affect the same entities in other cases. A test case includes
only the alert that triggered the event and is populated using existing data.
You can use it to simulate a playbook or test behavior on the **IDE** page.

To create a test case, follow these steps:

1. In the platform, go to the **Cases** page.
2. Select the required case.
3. Locate the target alert (on the **Alert** tab in the legacy experience, or within the alert details pane in the enhanced experience).
4. Click more_vert **Alert Options** and select **Ingest alert as test case**.
5. Select the required environment and click **Simulate**.
6. Refresh the page.

A new test case appears in the case queue or list view. It's marked with
the label **Test** on the case card and contains only one alert.

You can now use the test case in the Playbook Simulator, or the
**IDE testing** page.

> [!NOTE]
> **Note:** Any changes that you make to entity properties in the test case won't affect those entities outside the test case.

> [!CAUTION]
> **Caution:** A test case doesn't isolate external products. When you run a playbook on a test case, its actions still run against the connected products. For example, they can create tickets or block hosts. To prevent a playbook step from running live, turn on [Simulate mode](https://docs.cloud.google.com/chronicle/docs/soar/respond/working-with-playbooks/working-with-playbook-simulator.md.txt#simulate-mode) for that step.

**Need more help?** [Get answers from Community members and Google SecOps professionals.](https://security.googlecloudcommunity.com/)