> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/test-manager/working-with-test-suites.md).

# Working with Test Suites

## Description

A test suite is a collection of related test cases that you can manage and run as a single unit. You can execute and have the system run them together in a sequence. You can also create Sub-Test Suites, which are test suites within a test suite.

## Create a Test Suite

To create a test suite, click the folder icon from the navigation options on the left of the screen. Click the ***Create Test Suite*** button.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2ca4c7d6fda7b739d7af3b547b83970a6ff3bf38%2F6a1555fd-70fc-4f36-bb45-125429cbf13e.png?alt=media)

The system displays a *New Test Suite* popup screen. Enter the name of the test suite and a description to help you remember details about this test suite. Click ***Save*** to save the test suite.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-26cf44c92278058f6f0795b49ba0d5eb3a30cd76%2Fa7b91302-efde-4b57-9e93-14f8bc8e7659.png?alt=media)

When you create a test suite the system displays it in the tree view. You can then create new test cases in that suite or move existing text cases into it.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-9374d6517bc9b540583095c522b3876e7faf84be%2F11e6ce24-5391-4311-b850-0f9faf796409.png?alt=media)

The system displays the *Test Suite* view, which shows the test suite in the tree and the name of the test suite as a heading in the viewer, as well as any description you added when creating the suite. If you have not yet executed the test suite, the system will not show previous-run details. However, once you run the test suite, this screen also displays the run details of the last test suite execution.

## Move Test Cases

To move an existing test case or multiple test cases into a test suite, go to the main Test Manager screen and click the checkbox next to the test cases you want to move. Select the name of the test suite from the dropdown menu and click ***Move***.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-591e6e472221251c2d8b3592e8884a629b3d5f35%2F393c12d5-0e3f-467c-a61d-1fcc91adbcc5.png?alt=media)

## Clone a Test Suite

Once you have created a test suite folder, you can clone that folder. Select a test suite and click the ***Clone Test Suite*** button. The system displays a popup window with the name and description of the test suite you are cloning. Modify the fields and click ***Clone*** to confirm.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-8a4ab118a740a951498e70511478193d130cfaf8%2F32bcbb9b-d4ef-473e-a504-4d5280ea1a3a.png?alt=media)

The system saves the updates, clones the test suite and the associated test cases, and displays the cloned test suite in the tree.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-5904f4313c19dda72207c80ae5ff1592b5798977%2F001fff27-08ed-4941-a61b-3969f6eae781.png?alt=media)

## Run a Test Suite

You can run your test suites in the LogicNets Test Manager. Select a test suite and click the ***Run Test Suite*** button. The system displays a popup window with the name of the test suite and a dropdown menu with the list of target system in which to run the tests.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-ab8771ebcfe4c0bb49e1577eee1782d9a42ddc3a%2F33fad825-4056-4c30-92ab-ee5febb02e6b.png?alt=media)

When you click ***Run***, the system displays a popup window containing a list of all active test cases in the selected test suite. The system starts running the test cases in the order in which they occur in the test suite folder and displays the real-time status of each, showing in the *Details* column if a test case is running.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-15e64957fda04efa05fe02f771ed4d756a073780%2F8d9c1fea-2662-4945-9dbb-1f5f101436df.png?alt=media)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-dc280aa56046757d315c98757889f224d8649161%2F4cf89171-f490-428f-a9e5-9d1723d849f8.png?alt=media)

You can close the popup once the tests have all completed by clicking ***Close***. This closes the popup window and refreshes the tree. The system displays the status of the last execution. The system updates the previous run list with the latest details, including the date and time of the execution, status, and the target system. The *Run Details* section displays the status and details of each test case in the suite.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-040d2168917579f6b916a5d8d1ac45831790fdd4%2F43240a18-f5d4-4a42-b78a-9b70abf88682.png?alt=media)

If a test suite fails, the system shows a red *X* in the *Result* column next to the suite and includes details about the failure in the *Details* column.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2864c9fca4105185c2322000eb99a07cc5a6e4c5%2Fd15455fa-1553-4948-9e2f-c5f15bf7c3fd.png?alt=media)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-e0c6f51d1dfcf8f8e3be2ee49b8da5a7b5abe3c2%2F90840651-f31f-43ee-9200-361588bf0a12.png?alt=media)

## Delete a Test Suite

To delete a test suite, select the test suite you want to delete. Click the Delete Test Suite button and the system displays a popup window to confirm the action. When you delete a test suite, the system deletes the test suite, the associated test cases, and all previous-run results.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-352958a55feb06c96b15d4e75ea0c9dbae1b4e80%2F1606ec14-3ac4-45ac-ae43-aa2e1eaa84ce.png?alt=media)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/test-manager/working-with-test-suites.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.