# Testing your App

## Testing Your Application in eMOBIQ AI

Once you've built your application using **eMOBIQ AI** , it's essential to test it thoroughly before sharing it with others or deploying. Testing ensures your app works as expected — both visually and functionally.

There are **two primary ways to test your app** during the development process depending on what you selected during the creation of your application, specifically the `Docs & UI only` Button.

<figure><img src="https://1183608340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUDFGj32EEDxm4CJ43yZ%2Fuploads%2Fgit-blob-8768c252bbc6785d680e9911285a9d4f37670e7b%2Fimage%20(5)%20(1).png?alt=media" alt="" width="563"><figcaption></figcaption></figure>

{% hint style="danger" %}
*Enabling this generates the projects only up to the UI of your application and cannot yet be deployed or published until the full code functionality has been completed*
{% endhint %}

***

### 1. View How the App Looks (Docs & UI only Mode)

<figure><img src="https://1183608340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUDFGj32EEDxm4CJ43yZ%2Fuploads%2Fgit-blob-8e4a5bff81b9361e8dd2da8c03a048678345d8a4%2Fimage%20(47).png?alt=media" alt="" width="375"><figcaption></figcaption></figure>

#### What It Is:

**Docs & UI only Mode** , allows you to see how your app will look from a user’s perspective — without executing any backend logic or API calls.

It’s ideal for:

* Reviewing layout, design, and component positioning
* Ensuring responsive behaviour across screen sizes
* Sharing a visual prototype with stakeholders or team members

#### How to Use It:

* Click the `Test App` button in the eMOBIQ AI editor after the UI Agent has completed it's task
* You can also navigate to UI Pages to view the pages generated by eMOBIQ AI
* Interact with components like buttons, drop down menus, and inputs — but keep in mind these won’t trigger actual actions or data changes

#### Limitations:

* No real API calls are made
* Dynamic variables and backend logic aren’t executed
* You can’t test workflows, database queries, or integrations

{% hint style="info" %}
*Tip: Use this mode early in development to get feedback on design and flow, especially if you're still shaping the user experience*
{% endhint %}

***

### 2. Completed Project: Test Functionality and Debug Logic

#### What It Is:

Once your project has completed all 6 stages, your application becomes fully interactive. All components are connected to their underlying APIs, databases, and business logic, allowing you to test every feature end-to-end. However, do note that eMOBIQ AI might make mistakes so do check through what was generated and if your app needs to be further [debugged](https://docs.emobiq.com/emobiq-ai/readme/debug-agent).

<figure><img src="https://1183608340-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FsUDFGj32EEDxm4CJ43yZ%2Fuploads%2Fgit-blob-df97aee306e4dff41609bd6fbd228acf1358afe8%2Fimage%20(49).png?alt=media" alt="" width="365"><figcaption><p>Continue to complete your project after the Docs&#x26;UI Stage</p></figcaption></figure>

**It’s ideal for:**

* Testing API integrations and dynamic data flows
* Validating user interactions and event triggers
* Debugging issues in logic, variable mapping, or error handling

#### How to Use It:

* Click the `Debug` button
* The full version of your app will load, complete with all connected data sources and logic steps
* Perform typical user actions like submitting forms, clicking buttons, or navigating between screens

***

### Benefits of Using Docs & UI-Only Mode

While Full Build Mode allows for complete functional testing and debugging, there are distinct advantages to using **Docs & UI-Only mode** during the early stages of development — especially when working with AI-powered platforms like **eMOBIQ AI**.

#### 1. **Faster Feedback and Iteration**

Because Docs & UI-Only mode doesn’t execute backend logic or API calls, it loads instantly and allows users to see how the app will look and feel **without waiting for complex builds**.

This makes it ideal for:

* Sharing mockups with stakeholders
* Getting early feedback on layout and flow
* Validating user experience decisions before investing time in logic and integrations

{% hint style="info" %}
*Tip: Use this mode to iterate quickly on design changes, such as adjusting component placement, colour schemes, or responsive behaviour*
{% endhint %}

#### 2. **Lower Cost**

Running a full build that involves AI-generated logic, database queries, or external API calls increases the cost of platform usage credits.

In contrast, **Docs & UI-Only mode uses minimal resources** , making it a cost-effective way to:

* Preview app structure
* Share prototypes internally
* Explore different UI/UX directions without triggering expensive backend processes

This is especially valuable for teams or individuals who want to **explore multiple ideas** without incurring high costs per iteration.

#### 3. **Early Visibility Without Full Commitment**

You don’t always need to test every function to understand if an app is heading in the right direction. With Docs & UI-Only mode, you can:

* See how components are laid out
* Test navigation flows
* Understand how data will be presented (even if it’s not live yet)

This gives you a **preview of the final product** long before it’s fully functional — allowing you to make informed decisions earlier in the process.

***

### Final Thoughts

Understanding the difference between **Preview Mode** and a **Completed Project** helps you make the most of eMOBIQ AI’s powerful no-code development environment.

Use **Preview Mode** to refine the look and feel of your app early on, before continuing to develop your project to completion once your logic and integrations are ready — so you can ensure everything works exactly as intended.