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

# Testing your app

## Best practices for testing your app

When testing your app, think about what it might look like through the eyes of ShopBase merchants of varying skill levels. You should make sure you have accounted for any issues that might occur when a merchant installs your app in their store. Here are some suggestions of what to look for when you test your app:

* Make sure that the installation process is easy to understand and execute
* Make sure that your app can appropriately handle issues like 404s, unexpected inputs, and heavy user traffic.
* If your app interacts with or adds something to a merchant’s online store, then test your app with several different ShopBase-made themes.
* After you’ve installed your app on a development store, make sure you can uninstall and reinstall that app on the same shop.

## Installing an app on a development store

When a merchant installs your app, it must first authenticate with the merchant’s shop using OAuth. You can test this by installing your app on a development store. If you don’t have a development store, then you can create one in the partner dashboard.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://developers.shopbase.com/build-an-app/getting-your-app-approved/testing-your-app.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.