> For the complete documentation index, see [llms.txt](https://docs.healthuniverse.com/overview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.healthuniverse.com/overview/testing-your-app.md).

# Testing your app

After deploying or redeploying your app, follow these steps to test it and confirm everything is working as expected:

#### 1. Test Your Application

**For Streamlit apps:**

1. Go to your app on [Health Universe](https://www.healthuniverse.com/).
2. Click the **Launch App** button to open it in a new tab.
3. Interact with the app to confirm it’s running correctly and that your updates appear as expected.
4. You should also fill in the description information on the apps page so that others can understand the app and know how best to use it.

**For FastAPI apps:**

1. FastAPI apps do not launch directly from the app page — they are launched within Navigator.
   1. Launch Navigator
   2. Search for app (in search bar)
   3. Click "Use Tool"
   4. Run app.

#### 2. Review Deployment Logs (Optional but Recommended)

If something doesn’t look right, or just to be thorough:

1. In the **left-hand menu**, click **Deployments**.
2. Locate the **Production** deployment box.
3. Click **Build Logs** to review details of the most recent deployment.

> 🛠️ Use the logs to troubleshoot issues such as build errors, missing dependencies, or runtime exceptions.


---

# 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://docs.healthuniverse.com/overview/testing-your-app.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.