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

# Saving Generated Tests

> Decide whether generated tests land in the central library or go straight into a suite, and when each path is the right call.

## The two options

<img src="https://mintcdn.com/quashbugs/8CKl0mBxr-B3bXzO/images/image-4.png?fit=max&auto=format&n=8CKl0mBxr-B3bXzO&q=85&s=c51ec8927c888dd0b2eb9eec582ad105" alt="" width="1729" height="1010" data-path="images/image-4.png" />

## Save to Test Cases (recommended)

Saving to the Test Cases library adds your generated tests to a central repository at the workspace level. From there, they can be added to any number of suites, searched and filtered, edited, and reused across different projects and sprints.

**Use this when:**

* You are building a test library over time
* The tests might be used in more than one suite
* You want to organise, tag, and maintain tests centrally
* You are working on a feature that will have ongoing test coverage

**How:**

1. In the Tests panel, select the tests you want — individually or using **Select all**
2. Click **Save to Test Cases**
3. Tests appear in the Test Cases library immediately

## Add to Suite (faster)

Adding directly to a suite skips the library and places the tests straight into a specific suite, ready to run.

**Use this when:**

* You know exactly which suite these tests belong to
* The tests are for immediate, one-off execution
* Speed matters more than long-term organisation

**How:**

1. In the Tests panel, select the tests you want
2. Click **+ Add to Suite**
3. Choose an existing suite or create a new one
4. Tests are immediately added and ready to run

## Which to choose

If you are unsure, save to Test Cases. You can always add library tests to a suite later — it takes seconds. The reverse is harder: tests added directly to a suite without going through the library are harder to find, reuse, and maintain.

| Situation                                  | Recommended        |
| ------------------------------------------ | ------------------ |
| Building comprehensive coverage over time  | Save to Test Cases |
| Tests will be used in multiple suites      | Save to Test Cases |
| Working on a long-running feature          | Save to Test Cases |
| Running a quick one-off test immediately   | Add to Suite       |
| Specific suite needs these tests right now | Add to Suite       |
| Prototyping or exploring coverage          | Add to Suite       |

## Selecting tests before saving

You do not have to save everything Megumi generates. Review the Tests panel before saving.

* Click the **checkbox** on individual cards to select specific tests
* Click **Select all** at the top to grab everything
* The selected count appears at the bottom — e.g., "3 selected"
* Click **Clear** to deselect without saving

Review names, priorities, and descriptions before saving. If something needs adjustment, use a follow-up prompt to fix it in the session first, then save.

## After saving

Once tests are in the library, you can:

* Add them to any suite from the Test Cases list
* Edit instructions, expected results, priority, or type
* Tag them for filtering and organisation
* View which suites currently include them before making changes
* Export them for use in other tools

Tests saved from a recipe carry the name, priority, and description assigned during generation. You can edit any of these fields directly in the Test Cases library.