> For the complete documentation index, see [llms.txt](https://docs.oneweb.tech/oneweb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-ux-ui/ux-ui-test-and-debug-guideline.md).

# UX/UI Test & Debug guideline

AppDesigner provides an UI for displaying the server-side logs of events. User actions such as saving entity, fetching the available tables, views, sequences trigger server-side events. Logging provides real-time logging data.

Logging Interface, also known as Console, sits on the bottom of the entity page. It looks like

![Fig: AppDesigner Console](/files/YpwQ1HGoluKNvxK4IGrg)

**Console Characteristics** \
Green icon ![](/files/RH9CxMimPDrSZmW0uinv) means console is connected and user is entitled to engage with the real-time data. \
Data is synced with the current logged in user \
If data is changing too fast, then logging can be paused and can be downloaded

**User Events** \
Component Properties Box \
Save Entity \
Listing of 

* Database tables 
* Database sequences 
*  Database views Actions

**Logging Levels** \
AppDesigner provides logging for the following levels - \
      INFO \
      DEBUG \
      ERROR

**How to Debug** \
Extracting data can be tricky, but it can give insight into the usability of the AppDesigner. As user triggers some UI actions (listed above), there is corresponding server-side events. User can monitor those events for success or error. If user finds that events are displaying too fast, then user can pause or download the log file and analyze locally.


---

# 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:

```
GET https://docs.oneweb.tech/oneweb/design-and-develop-oneweb-apps/design-and-develop-ux-ui/ux-ui-test-and-debug-guideline.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.