> 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/the-logicnets-designer/test-a-logicnet.md).

# Test a Logicnet

Testing a logicnet not only allows you to see what users will see, but it also allows you to test all the background processes to make sure that they work as you intended. Testing at the logicnet level allows you to see if the questions flow in the order intended, and testing at the project level allows you to test the logicnets, CSS, JavaScript, and data elements are working with the project as a whole.

Regardless of the testing level, another useful feature of testing is to view the underlying data. See the article on Context Data for more information on this.

## Test at the Logicnet Level

Testing at the logicnet level is often used for short tests to verify a small piece of functionality is working correctly. Because testing at the logicnet level does not include any framework styling or any other features offered in LogicNets' frameworks, it is more often used to test a piece of data processing rather than the UI of an application.

1\. Click on the logicnet you want to test.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-2cd47fef8a291e0bbc63c4033fcd239e177bd466%2F304d0cb0-16b9-4b4d-a46d-c3dee3b006e9.png?alt=media)

2\. Click **Test** from the *Designer* tab or from the *Details* tab.

3\. The system opens a new browser window or tab with the logicnet in it. Click through the test version to see your application the way users will.

4\. To close the test, close the new browser window or tab.

## Test at the Project Level

If you are using a framework in your application, you need to test your application at the project level so you see what end-users will see when they run the application.

1\. Click the name of your project and click **Test** from the *Details* tab.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-c04fcce43543b60b5235e088e8c2527251a17658%2F2d3a6e7c-6ef7-42d4-93c5-3e0b675d1f0a.png?alt=media)

2\. The system opens a new browser window or tab with the logicnet in it. Click through the test version to see your application the way users will.

3\. To close the test, close the new browser window or tab.

## Testing Standalone Projects (Advanced)

If you are working on an application that does not use a framework, to test your application at the project level you must first indicate your start logicnet for the project.

1\. In the *Projects* pane click on the name of the project you want to test.

2\. Click **Modify** in the *Details* tab.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-92b8dfe8b07f3a439b5ffcdbe4345cfd9481d26b%2Ff06710d2-2746-4cd6-a16c-d4f56191c6b8.png?alt=media)

3\. Click the **...** button next to *Start Logicnet*.

![](https://2802811211-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FdFhfexCjZ5JMhwGzzywq%2Fuploads%2Fgit-blob-616dfc88cdbbe4399bc614b638f666d80508b5fe%2Fb99c1e4f-9977-41a1-b0db-3e49f11727a9.png?alt=media)

4\. Click the name of the logicnet you want to be the first one the system runs when you run your application.

5\. Click **save** at the top of the *Details* tab.

6\. Click **Test** at the top of the *Details* tab.

7\. The system opens a new browser window or tab with the logicnet in it. Click through the test version to see your application the way users will.

8\. To close the test, close the new browser window or tab.


---

# 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/the-logicnets-designer/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.