> 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/getting-started/interacting-with-nodes-in-the-designer-viewer/test-a-logicnet.md).

# Test a Logicnet

To test your project and logicnets you use the ***test***, ***debug***, and ***debugger*** options. Click the arrow on the test button and a dropdown menu of these test options appears. Click the one you want to use.

* *Test* runs your logicnet, always beginning from the start circle. The system does not run any logicnet that is not called from this logicnet. Note: You test a framework by clicking the ***TEST*** button at the project level.
* *Debug* runs your logicnet but additionally displays messages that may help you debug if your project is not working as you may have expected.
* *Debugger* opens a new window and shows a much more detailed suite of debugging tools. Note: Debugger is not available in all user profiles and is an advanced feature of the LogicNets Designer.

Most users use the test button almost exclusively, in conjunction with the *DATA* tab, for troubleshooting purposes.


---

# 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/getting-started/interacting-with-nodes-in-the-designer-viewer/test-a-logicnet.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.