> For the complete documentation index, see [llms.txt](https://docs.stylemixthemes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stylemixthemes.com/motors-app-documentation/motors-application-build/test-your-app-on-mac.md).
# Test Your App on mac
In this section, we are going to describe how to build the test **APK file**.
There two ways of testing your app: via **Android Studio Emulator or by generating Test APK.**
After you added **app icon** and **website URL** you can launch Emulator by clicking on **Run App** button in the **Toolbar**.
After that the Emulator will be launched with the app.
If you'd like to test the application on physical android devices, you can create APK file.
For this, you need to go to **Build > Build Bundle(s) / APK(s) > Build APK(s)**
This will lead to the app-building process, and once it finished Android Studio will display a specific notification in the bottom right corner.
The link Locate opens the folder where the APK file is stored. Or you can follow this path to find this file: Project folder > Android > App > Release
Another way to build test apk is to run these commands in Android studio terminal
{% hint style="info" %}
flutter build apk --no-sound-null-safety - debug
flutter build appbundle --no-sound-null-safety - release
{% endhint %}
---
# 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.stylemixthemes.com/motors-app-documentation/motors-application-build/test-your-app-on-mac.md?ask=&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.
