Skip to content

Components

Mobile Devices

Up to 24 devices per TEO-Client PC can be connected via 4x USBHUB’s (6x OR 8x USB ports per USBHUB). All phones will have to be “enabled” for automation. Details on phone preparation can be found below under Phone Settings chapter.

Supported Devices

The supported phones, OS versions and MCM modems are listed on Supported devices.

Dedicated USB-HUB

It is advisable to use a high-quality USB-HUB with an external power supply. USB-A to USB-C adaptors might be required

Quad TEO Agent

The Quad TEO Agent is installed locally on the PC that connects all mobile phones via a dedicated USB-HUB. Its main functions include:

Main Functions

Bridge Creation

  • Creates a bridge between the local machine and the Quad TEO AWS server.

Centralized Trace Server Connection

  • Connects to the centralized trace server to collect specific traces (if in scope).

Automatic Device Discovery

  • Automatically discovers new mobile devices when they are connected.
  • Creates a new Mobile ID on the WEB UI.
  • IMSI and IMEI start as placeholders and have to be edited by hand; so does the MSISDN when the agent cannot read it from the phone. See Automatic Device Discovery.

Remote Mobile Phone Control

  • Allows remote control of mobile phones from any location via the QTEO UI interface.

How Quad TEO Agent Works

The Quad TEO Agent integrates advanced mechanisms to ensure efficient device management, communication, and monitoring.

1. SQS (Simple Queue Service) Integration

  • Utilizes Amazon SQS for reliable message handling between the agent and the Quad TEO AWS server.
  • Ensures messages are queued and processed in a robust and fail-safe manner.

2. Heartbeat Monitoring

  • Sends a heartbeat every 60 seconds to confirm the agent is active and connected.
  • Enables the system to detect and respond to connection issues promptly: the Dashboard map shows a node as unknown after about 72 seconds without a heartbeat and as offline after two minutes.

3. Device Monitoring

  • Health check every 30 seconds: checks that Appium is healthy and that each connected phone and MCM modem responds.
  • Housekeeping every 10 minutes (and right after a new device connects): reads each device's details such as IMEI, MSISDN, IMSI, operator, model, OS and time zone. These values are not written back to the Mobile ID; keep the Mobile ID fields up to date by hand.
  • Automatic recovery: a phone that shows up as unauthorized or offline is reconnected (adb reconnect), and Appium is restarted when it stops responding.
  • The device state, battery, temperature and signal feed the Dashboard Status page and the Prometheus metrics.

Quad TEO GUI

The GUI server is on AWS and its main functions are:

Main Functions

  • Add and manage test nodes.

  • Add and manage Mobile IDs.

  • Add and manage MCMs

  • Monitoring and using Mobile IDs.

  • Monitoring and using MCMs.

  • Create a temporary URL to share connected devices with others.

  • With the projection feature, entities can be assigned to projects for customization.

  • Add and manage External APIs

  • Add and manage Trace Filters

  • Create test cases.

  • Create and manage test suites.

  • Assign weights to test cases assigned to test suites.

  • Run Executions / Check Results / Download

  • Analyze results and statuses in detail on the Statistics and Status pages.