> 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-cases.md).

# Working with Test Cases

## Description

A test case is a set of actions or instructions that help confirm whether your LogicNets-based application is working as expected. It consists of one or more steps that the system executes in a sequence. The system can execute a test case by itself or as part of a suite of test cases.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-f2d5bef6950606ce8f9a85cc335a913f532fbe81%2F04d11bb8-d537-474a-b81a-ff1ff0f01e4d.png?alt=media)

When you select a test case from the *Test Suite* menu, the system displays the test case view. The first section in this view displays the details of the test case, including its name, description, when it was created and by whom, revision, and request URL. The second section displays the request and response along with the headers.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a4376a583f30e4bfae5bc05e1c4c9384095f2af4%2F8201b6b3-497b-4957-858c-ac9f91483c3a.png?alt=media)

The third section, *Run Details,* shows the list of all previous runs of that test case.

## Create an Empty Test Case

To create a new test case, start by creating/selecting the test suite in which you want to create the test case. Click ***Create Empty Test Case***. The system opens a popup window where you can enter the details for your new test case. Enter the name, description, and the associated URL.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-58b38f94505cf465f10181ebd544c96e7788db92%2Fc1b3a209-b2a2-4482-9338-e7080c5f626d.png?alt=media)

Once you have entered the details, click ***Create*** and the system creates the empty test case. To begin setting up the test case, click ***Modify Test Case***. Enter the test details in the appropriate tabs: *Request*, *Response*, *Request Headers*, *Response Headers*.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-4a375475143f45211acd59672b3260130270add1%2F16fc1b1e-c4c9-4995-8d08-9afb8dd2757e.png?alt=media)

## Modify a Test Case

To modify an existing test case, select the test case and click ***Modify Test Case***. Make changes to modifiable fields and click ***Save***. The system increments the revision number by 1 and updates the last modified date and time.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-07166fc4cad7336658a62d3a336bcea9ecef9ff7%2F3ebfcfbd-6bdb-4726-9cf1-f641363f676f.png?alt=media)

## Clone a Test Case

To clone a test case, select a test case and click ***Clone Test Case***. The system displays the name and description of the test case you are cloning. Change the name and update the details and click ***Clone***. The system will add the test case to the same test suite as the original test case.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2e6168dbb97bc3a53cc7bcf2eba8aa37aad45a6b%2F63840ce3-497f-41da-b218-256ad79d08e3.png?alt=media)

## Run a Test Case

You can run an individual test case, even it if is part of a test suite. To run a single test case, expand the test suites in the tree view to display the test cases within a test suite. Click the test case you want to run and click the ***Run Test Case*** button.

The system displays a popup window with the name of the test case and a dropdown menu containing the list of target systems against which to run the test. Click ***Run*** to start the test case.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-e7fcda3c274a39bdface96455230726613cfe43d%2F1a3356e3-7083-4449-a0d6-b2302f3fed65.png?alt=media)

The system displays the real-time status of the test case. If the test case is running, the system says that in the *Details* column.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-fbcd6e21b0f3077db74308fbc96704f5299153fd%2F31b7fb52-86a3-43e4-a94b-7a39ce4af8ee.png?alt=media)

Once the execution is finished, the system displays the status and run details.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-3d9f159384358aedcfd817bb8d6151421b550d70%2F8e83ef91-1d85-4f62-9c68-c9c914bf4b57.png?alt=media)

If a test fails, the system displays an error.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-49f956798dacd6f822e03eb66bf546f59f054fb6%2F2cc9961a-6d79-42fa-98e5-513d55d001ad.png?alt=media)

When you close the popup screen, the system refreshes the tree and displays the status of the last execution. The run details section displays the status and details of the run.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-de4114022f80219d30978134300849896900de07%2F893cd389-0bae-4d84-b96e-38e10c3a32e4.png?alt=media)

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-be7fff1934a28f4ac49baf9cc8fde62c328d82bb%2F0736ea91-3a70-47d2-8372-b1199b17ad2b.png?alt=media)

## Deactivate/Activate a Test Case

To deactivate a test case in a test suite instead of deleting it, select the test case and click ***Deactivate Test Case***. While that test case is deactivated, the system will skip it when executing the test suite in which it is located. You are also not able to run the test case individually.

To reactivate a deactivated test case, click the test case and click ***Activate Test Case***.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-6cd9ea688a666c50f25413347156cf0ffcd08f04%2F28c0b794-f83b-4366-9ed0-10611f3e8542.png?alt=media)

## Delete a Test Case

To permanently delete a test case, click the test case to delete. Click ***Delete Test Case*** and the system displays a popup window asking you to confirm the deletion.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-a61210e79869fbacbcc72ed2411d504822fe6e9e%2F78709c4d-cf83-4b43-b7f8-66abe1254ccd.png?alt=media)

## Archived replies

### Tim Cowlishaw, 2024-12-12

Patrick's comment (now hidden from users).

You need to describe how a test case is created in the first place. Not the mechanics of using this feature, but where the request content to be tested comes from. If that is explained somewhere else that I can't find, then include a link.


---

# 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-cases.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.