> For the complete documentation index, see [llms.txt](https://mozarkdocs.gitbook.io/appx_documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/interactive-testing/overview.md).

# Overview

## Interactive Testing

Use this page to launch and run live manual test sessions across web, mobile, and TV platforms.

{% hint style="info" %}
Interactive Testing sessions open in a separate browser window or application provided by Mozark's session infrastructure.

The Testing Portal handles configuration and session tracking.

The live device view runs in that separate window.
{% endhint %}

### Web Testing

Test websites and web applications in real browsers running on real operating systems.

#### Launching a Web Session

Navigate to **Interactive → Web** in the sidebar.

The configuration screen uses four selection columns.

Complete them from left to right.

Each column becomes active only after the previous one is filled.

1. **Operating System** Select the OS family, such as Windows or macOS.

   Then select a specific version, such as Windows 11, Windows 10, or macOS Sonoma.

   Options shown in gray are temporarily unavailable.
2. **Browser** Select the browser.

   Available options include Chrome, Firefox, Edge, and Safari.

   Safari availability depends on the selected OS.

   Options with no available versions appear disabled.
3. **Browser Version** Select the specific browser version.

   Newer versions appear first.

   Unavailable versions appear grayed out.
4. **Resolution** Select the screen resolution for the session, such as `1920×1080`.

   Available resolutions depend on the selected browser and OS.
5. **Launch Session** Click **Launch Session** in the top-right corner.

   The portal contacts the session service, allocates a remote machine, and redirects you to the live session.

   If all slots are occupied, the portal shows an error toast.

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

{% hint style="warning" %}
Do not close the configuration tab immediately after launch.

The redirect to the live session window happens automatically.

If you close the tab before the redirect completes, the session can become orphaned and may not appear in session history.
{% endhint %}

#### Configuration Auto-Selection

When you open the Web selection page, the portal automatically preselects the first available option in each column.

You can launch immediately with the default configuration.

Change values only when you need a specific setup.

### Mobile Testing

Test native Android and iOS applications on real device configurations.

Navigate to **Interactive → Mobile**.

The selection screen works like Web testing, but uses a device-oriented layout.

1. **Select Platform** Choose **iOS** or **Android**.
2. **Select Device Brand** Review the available manufacturers for the selected platform.
3. **Select Device Model** Choose from the available models for that brand.

   Each model card shows the device name and relevant specifications.
4. **Launch Session** Click **Launch** to start the live device session.

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

### TV Testing

Test connected TV and OTT applications on real TV device configurations.

Navigate to **Interactive → TV**.

The selection screen mirrors the mobile layout.

Select the TV brand and model, then launch the session.

TV sessions use a dedicated routing path within Mozark's infrastructure.

<figure><img src="/files/65Usw2CK6KLkgF9sLvZr" alt=""><figcaption></figcaption></figure>

### What happens during a session

Once launched, the live session opens in the Mozark session runner in a separate window or tab.

Within the runner, you can:

* Interact with the device or browser normally.
* Take screenshots that stay linked to the session.
* File bugs directly from the session runner toolbar.
* End the session when testing is complete.

#### Stream panel actions

Interactions with the stream panel are translated into real device actions.

| Stream panel action | Device action                             |
| ------------------- | ----------------------------------------- |
| Single click or tap | Touch tap at the corresponding coordinate |
| Click and drag      | Swipe gesture along the drag path         |
| Scroll wheel        | Scroll gesture                            |
| Keyboard typing     | Text input on the focused element         |
| Long click and hold | Long press gesture                        |

#### Action toolbar

The toolbar above the video stream contains session controls.

* **Screenshot** captures and downloads a full-resolution screenshot of the current screen.
* **Start Recording** and **Stop Recording** begin or end session video recording.
* **Home**, **Back**, and **Menu** send the corresponding hardware button press to the device.
* **End Session** cleanly terminates the session and releases the device back to the available pool.

Recordings are saved automatically and appear in the session's Downloads section after the session ends.

#### Ending a session

To end a session, click **End Session** in the toolbar or close the browser tab.

The platform marks the session as complete.

It then uploads recordings, logs, and screenshots automatically.

You can access them later from the Session Summary screen.

If a session stays idle longer than the configured timeout, the platform ends it automatically and releases the device.

The default idle timeout is typically 10 minutes.

The portal automatically saves the session recording, screenshots, and filed bugs.

You can review them later from the Sessions list or the Session Details page.

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


---

# 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://mozarkdocs.gitbook.io/appx_documentation/test-infrastructure-documentation/interactive-testing/overview.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.