> For the complete documentation index, see [llms.txt](https://docs.decisionrules.io/doc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decisionrules.io/doc/space/tests/tests-tab.md).

# Tests Tab

The Tests tab is your central workspace for organizing, managing, and executing test data. Here, users can view the entire testing hierarchy, create new Test Suites and Tests, reorganize existing items, and trigger test executions.

### Structure and Selection

The interface uses an expandable structure containing:

* Rules
* Test Suites
* Tests

{% hint style="info" %}

#### Better management

Selection operates via checkboxes. Selecting a parent item automatically selects all of its descendants.
{% endhint %}

### Create Test Suite

Users can create new Test Suites directly from this tab to prepare testing structures for existing rules.

1. Click the Create button.
2. Select Test Suite.
3. Select target Rule.
4. Click Create Test Suite.

<figure><img src="/files/6QI4rgsm4aR8sSt953iz" alt=""><figcaption></figcaption></figure>

### Creating a Test&#x20;

The process for creating a Test is similar but requires defining the specific test scenario:

1. Click the Create button.
2. Select Test.
3. In the modal window, choose the Rule and Test Suite *(Note: The Test Suite must be created beforehand)*.
4. Configure your test details in the respective tabs:
   * Metadata tab: Update the test name.
   * Input tab: Define the input parameters and strategy.
   * Output tab: Review or configure the expected outputs.
5. (Optional) Configure Ignored Outputs: Use this to exclude dynamic values—such as current timestamps or generated IDs—that would otherwise cause false validation failures.
6. Click Save.

<figure><img src="/files/b1CcqmKyuNNmrwj3DFN0" alt=""><figcaption></figcaption></figure>

{% hint style="success" icon="bicep" %}

#### Best Practice

While you can create tests manually on this page, we highly recommend creating tests directly from the Test Bench during rule development for a more efficient workflow. Learn more about this approach in the [Rule Testing](/doc/rules/common-rule-features/rule-testing.md) documentation.
{% endhint %}

### Running Tests

Users can trigger test executions directly from this view:

1. Select the desired Tests or Test Suites using the checkboxes.
2. Click Run selected to execute only the chosen items.
3. *(If no items are selected, you can click Run all to execute all tests visible in the structure)*

### Moving Tests and Test Suites&#x20;

You can easily reorganize your tests and suites using two methods:

* Drag and Drop: Quickly move or reorder individual tests and test suites directly within the interface.
* Dropdown Menu: To move an entire Test Suite to a different rule, open the suite's detail view and select the target rule from the dropdown menu.

### Cloning (Copying)

Copy actions allow users to reassign tests or Test Suites to a different rule.

1. Select the desired test or Test Suite.
2. Click Clone

### Orphaned Tests

Orphaned Tests occur when the stored rule alias and version do not match any existing rule in the space.

* They are displayed in the space-level menu.
* Users can resolve them by selecting the orphaned tests and using the Move action to assign them to an existing rule.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.decisionrules.io/doc/space/tests/tests-tab.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.