> 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/test-manager-dashboard.md).

# Test Manager Dashboard

## Description

The purpose of the Test Manager dashboard is to be able to see a centralized view of which tests are currently running and the status of all target servers that are coupled to the test manager.

## Active Test Runs

A test run can contain test suites or a single test step, and the Active Test Runs section displays any test runs that are currently running. When the system is running a test, you can click to see details and you can also abort the test. However, if the system is running a single test step, the Abort button is disabled, because the system aborts tests starting with the step following the one it was on when you click that button.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-8136e9f8fff51e0742bb8802700d823516469bda%2Fd357e7f2-028a-43f3-ac3b-8b376be0e82d.png?alt=media)

When a test is running and there are no failed test steps the active test run bar is blue. Once one step of the test run fails, the bar turns red.

## Previous Test Runs

For every configured target server, the system displays a box containing information about the latest test runs. A red border around the box indicates that the last test run on this server failed. A green border indicates that the last test run succeeded. Each test run line item contains additional details of every executed test step.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-710ab92b541d3421dc89d6c7bfa1c0833c54c21f%2F0e37368d-6cbc-4d32-a14a-28b7a26911c3.png?alt=media)

You can configure target servers in Access Management as an outbound connection account with the purpose of “Execute test case”. These are servers on which the system can execute test runs from within the test manager, see [Working with Test Suites](/release-9/platform-documentation/test-manager/working-with-test-suites.md#run-a-test-suite). The server on which the test manager is installed is added as a target server by default.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-8bfcd2854de3ab60cbc20a5f51cd0746544d921f%2F25fe967d-1904-4304-9c5a-109a3bcad74b.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/test-manager-dashboard.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.
