> 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/logicnets-software-component-details/content-authoring-software-parts/test-manager-ln-tem.md).

# Test Manager (LN-TEM)

## License Basis: Per organization

Notes:

1. Allows Designer users to setup, run, and manage automated application test suites matching combinations of application input options with expected result outputs that can be used for high-volume regression testing in response to updates in modeled content, LogicNets frameworks and other components, or the system environment.
2. While supporting any generic combinations of test data, the Test Manager includes specific functionality to optimize FHIR application testing. Similar support for additional formats will be available in the future
3. Must be ordered at the organizational level as part of the Enterprise Authoring Bundle (EAB)

## LN-TEM Description

The LogicNets Test Manager is designed to optimize the integration of LogicNets applications into the workflow, reduce the effort of developing and maintaining test scripts, and provide a seamless integration with the full LogicNets suite.

The Test Manager is a stand-alone application that runs on a LogicNets server outside the LogicNets Designer environment. For applications that generate digital output rendered in common formats (particularly FHIR), it allows LogicNets designers to create, run, and manage persistent test suites. These can cover a full range of application input scenarios which are matched to the expected/required results to be generated by the application for regression testing as either the application or external factors change. The Test Manager can work with any text-based content, such as XML or JSON. However, it is optimized for FHIR applications, recognizing and properly handling variable elements such as response date/time stamps as well as providing a FHIR Questionnaire-based interactive test harness. Additional formats will be added in future versions. The Test Manager also supports testing across multiple languages when LogicNets applications are delivered with the Multi-Language Support module (LN-MLS)

Running interactively from the LogicNets user portal or invoked via an API, the Test Manager can perform automated tests and code validation on LogicNets FHIR-based published packages on either the local LogicNets instance or on a remote LogicNets server. The Test Manager is integrated with the LogicNets Designer and the FHIR test harnesses provided with LogicNets FHIR Questionnaire Export (FQE) and Runtime (FQR) components so that designers can identify particular requests and responses and then have them added as new test cases with the push of a button. The Test Manager also includes the ability to specifically validate system-generated FHIR and Web API requests as a component of testing.

## Services and Deployment Considerations

No additional services are required for basic deployment of Test Manager. Optional LogicNets Training Services (LN-TS) are available to teach designer users how to use the module.

PG-CO5-260217


---

# 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/logicnets-software-component-details/content-authoring-software-parts/test-manager-ln-tem.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.