> For the complete documentation index, see [llms.txt](https://docs.customerglu.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.customerglu.com/sdk/mobile-sdks/how-to-test-integration.md).

# How to Test Integration?

The client-side Integration Test Page can be used to verify the various integration steps on a physical device or Simulator.

<figure><img src="/files/spgw2ARt4yr0uyDAch3b" alt="" width="280"><figcaption><p>Client-Side Integration Test Page</p></figcaption></figure>

### **Triggering the Test Page**

The test page can be triggered via two methods:

#### **1. Via SDK Method**

{% tabs %}
{% tab title="Android" %}

```java
customerglu.testIntegration()
```

{% endtab %}

{% tab title="iOS" %}

```swift
customerglu.testIntegration()
```

{% endtab %}

{% tab title="Flutter" %}

```dart
CustomergluPlugin.testIntegration()
```

{% endtab %}

{% tab title="React Native" %}

<pre class="language-java"><code class="lang-java">import {testIntegration} from '@customerglu/react-native-customerglu';

testIntegration()
<strong>
</strong></code></pre>

{% endtab %}
{% endtabs %}

#### **2. Via the Dashboard**

* Open the Dev Console in CustomerGlu Dashoard

<figure><img src="/files/v7WScMzjlGhFFwMKpadU" alt=""><figcaption></figcaption></figure>

* In Integrations Page, Click on the Gear icon next to the SDK section

<figure><img src="/files/iWqIm54XNfN3hbeSL1H5" alt=""><figcaption></figcaption></figure>

* Click on the Test Integration button and enter the **userId** that is registered with CustomerGlu

<figure><img src="/files/LVuvNgakhjc3qmvSWpo4" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/7VD5pnJxgKbc4eAe41Vj" alt=""><figcaption></figcaption></figure>

{% hint style="warning" %}
**Note:** The app needs to be in a running/opened state for the test page to show up.
{% 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 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://docs.customerglu.com/sdk/mobile-sdks/how-to-test-integration.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.