> 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/using-the-test-manager-required-configuration-steps.md).

# Using the Test Manager: Required Configuration Steps

To use the LogicNets Test Manager with the Assessment Framework applications you must first set up a few things in Access Management. These steps assume that your installation build includes the Test Manager (LN-TEM).

## Access Management Configuration

Open Access Management and navigate to the *Group* tab, which is the second icon down in the navigation bar. Find or create the group for users who need access to the testing workflow, and make the following changes in the *Modify* screen:

1. Make your group a member of the **system.test-managers** group, which is available by default.
2. Add the **Test Manager** package to the Dashboard.
3. Add the following group roles to the **AssessmentFrameworkFHIRQ** category:
   * Add **api** role.
   * Add **addtestcase** role.
4. Click ***Save*** after making your changes.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-702bfe12707bda88f3e0d61c3067d400f6c508e7%2F3a1e1441-0ce4-46ab-b813-1e5c6289d437.png?alt=media)

## Project Configuration

To use Assessment Framework applications with the Test Manager and with the FHIRQ Executor comparison tool, change the project framework to *AssessmentFrameworkFHIRQ*. This will not impact your ability to test the project user interface using the ***Test*** button.

1. Click ***Modify*** to update the project details.
2. Select *AssessmentFrameworkFHIRQ* from the list. \*
3. (Optionally) set a default startcode for the project. The Test Manager requires a published project with startcode, but you can also customize the startcode when you publish the application.
4. Publish the project in preparation for creating/running test cases.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-350b37e1bb12f8d816c67c025004b97a9eb8c1e1%2F22b8c815-1357-44bb-a1ca-696d8cc2139a.png?alt=media)

\* To use the Test Manager with other frameworks, such as Web Services, and other comparison tools please talk to your LogicNets Representative.

## FHIR Test Client

After you complete the steps above, you can work directly with the Test Manager and the FHIR Test Client.

The FHIR Test Client is a tool that uses FHIRQ to run your Assessment Framework application as a series of requests/responses that can be fixed as Test Cases, in preparation for running against future versions of your application.

You can invoke the FHIR Test Client in a new browser tab using the following URL:

```
https://[installation_root/company]/project_startcode/api/fhirqtestclient

e.g. https://myinstallation.logicnets.net/mycompany/LogicNetsASF101/api/fhirtestclient
```

See the additional articles on Test Manager for instructions on how to work with the Test Manager.


---

# 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/using-the-test-manager-required-configuration-steps.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.