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

# Cases

> Creating and managing test cases for your evaluations

Test cases define the inputs your flow receives during an evaluation run. Each case represents a specific scenario you want to verify.

## Creating Cases

A user can choose to create a case from scratch or from a previous successful run.

### From Scratch

<Steps>
  <Step title="Open the test detail view">
    Navigate to the test where you want to add a case and click **Add case**.
  </Step>

  <Step title="Set a name">
    Give the case a descriptive label (e.g., "Short product description", "Edge case: empty input").
  </Step>

  <Step title="Fill in the inputs">
    Provide values for each of the flow's input connectors. The form automatically shows the input fields defined in your flow.
  </Step>

  <Step title="Set evaluator values">
    Provide the values needed for each evaluator to perform its check. They may come with a default set on the evaluator, but can be overridden per case to match the expected result for that specific scenario. See [Per-Case Overrides](/platform/tests/evaluators#per-case-overrides) for details.
  </Step>
</Steps>

<img src="https://mintcdn.com/spot-16018069/r-GexOMmWfMkx6yW/images/tests/case.png?fit=max&auto=format&n=r-GexOMmWfMkx6yW&q=85&s=2400c6d596ad287b2886ae877cf13848" alt="Case editor" width="2796" height="1652" data-path="images/tests/case.png" />

### From a Previous Run

<Steps>
  <Step title="Open the past runs">
    Navigate to the **Past runs** tab of your flow.
  </Step>

  <Step title="Create a case from a run">
    Find a completed run that represents a good test scenario and click the <Icon icon="flask-conical" size={16} /> icon on that row. This will pre-fill the case inputs with the values used in that run.
  </Step>

  <Step title="Select a test and review">
    Choose which test to add the case to, or create a new one, and save.
  </Step>
</Steps>

<Note>
  You can also reach the **Past runs** from inside a test — click the dropdown next to **Add case** and select **Import from runs**.
</Note>

### Managing Inputs

Test case inputs map directly to your flow's input connectors. When your flow has multiple inputs (e.g., a text input and a file input), each one appears as a separate field in the case editor.

<Note>
  Inputs marked as **not visible when running** (fixed inputs with the "Visible when running" toggle disabled) are automatically hidden from the case editor. The flow uses their fixed value during execution -- you do not need to provide them. If a fixed input is still visible when running, its value is pre-filled but can be overridden per case.
</Note>

<Warning>
  If you modify your flow's inputs after creating cases, existing cases may become **invalid** -- the evaluation will flag them with an error status so you can update them.
</Warning>

### Evaluator Overrides

Some evaluators have properties that can be **overridden per case**. The value you set on the evaluator acts as the default, but you can customize it for individual cases without creating a separate evaluator.

Overridable properties appear in the **Evaluator overrides** section at the bottom of the case editor. Only properties marked as overridable on the evaluator are shown -- see the [Evaluators](/platform/tests/evaluators) page for which properties support this.

### Bulk Operations

You can select multiple cases using the checkboxes in the cases table to perform bulk actions:

* **Run selected** -- execute evaluations only for the selected cases.
* **Delete selected** -- remove multiple cases at once.

## Running Cases

You can run cases in several ways:

* **Run all** -- from the test detail view, click **Run all** to execute every case in the test at once.
* **Run from the table** -- click the <Icon icon="play" size={14} /> button on a specific case row to run just that case.
* **Run from inside a case** -- open a case and click **Run** to execute it individually and see the results in real time.
* **Run a selection** -- select multiple cases using the checkboxes and use the **Run** bulk action.

<Note>
  You must have at least one evaluator configured in the test before you can run any cases. The run buttons will be disabled until an evaluator is added.
</Note>

To learn more about running evaluations, interpreting results, and handling errors, see [Running Tests](/platform/tests/running-tests).

### Status Indicators

Each case in the table shows its current status:

| Status                                                                                                                                                                                                                     | Meaning                                                                                |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| <span className="inline-flex items-center px-2.5 py-0.5 text-xs font-medium rounded-md bg-green-100 text-green-800">Passed</span>                                                                                          | All evaluators passed.                                                                 |
| <span className="inline-flex items-center px-2.5 py-0.5 text-xs font-medium rounded-md bg-red-50 text-red-600">Failed</span>                                                                                               | One or more evaluators failed.                                                         |
| <span className="inline-flex items-center gap-1.5 px-2.5 py-0.5 text-xs font-medium rounded-md border border-gray-200 !bg-[#FFFFFF] !text-[#1E1E1E]">Error</span> <Icon icon="triangle-alert" size={14} color="#eab308" /> | The flow failed to execute before evaluators could run.                                |
| <span className="inline-flex items-center gap-1 px-2.5 py-0.5 text-xs font-medium rounded-md border border-gray-200 !bg-[#FFFFFF] !text-[#1E1E1E]"><Icon icon="loader-circle" size={12} color="#1E1E1E" /> Running</span>  | Evaluation is in progress.                                                             |
| <span className="inline-flex items-center px-2.5 py-0.5 text-xs font-medium rounded-md border border-gray-200 !bg-[#FFFFFF] !text-[#1E1E1E]">Not run</span>                                                                | No results exist yet.                                                                  |
| <span className="inline-flex items-center px-2.5 py-0.5 text-xs font-medium rounded-md border border-gray-200 !bg-[#FFFFFF] !text-[#1E1E1E]">Cancelled</span>                                                              | The run was cancelled.                                                                 |
| <span className="inline-flex items-center gap-1 text-xs font-medium text-gray-700 dark:text-gray-300">— <Icon icon="triangle-alert" size={14} color="#eab308" /></span>                                                    | Results are outdated -- the flow, evaluators, or case data changed since the last run. |