DroidTest

What It Does

DroidTest is a command-line runner for Android device diagnostics. You give it a list of adb subcommands, it runs them all, and gives you a clean pass/fail report.

1

python DroidTest.py -v --timeout 8 --json report.json

  _____            _     _ _______        _
 |  __ \          (_)   | |__   __|      | |
 | |  | |_ __ ___  _  __| |  | | ___  ___| |_ ___ _ __
 | |  | | '__/ _ \| |/ _` |  | |/ _ \/ __| __/ _ \ '__|
 | |__| | | | (_) | | (_| |  | |  __/\__ \ ||  __/ |
 |_____/|_|  \___/|_|\__,_|  |_|\___||___/\__\___|_|

PASS: shell getprop ro.product.model
PASS: shell dumpsys battery
FAIL: shell dumpsys proximity
PASS: shell wm size
...

Summary: 31 passed, 3 failed, 34 total

The Problem It Solves

Testing an Android device’s hardware and software state manually means typing adb shell ... dozens of times, reading the output, and keeping track of what passed. That’s tedious and error-prone.

DroidTest automates the loop: define your test list once, run it, get a structured report. Useful for:

• Verifying a device after flashing a custom ROM
• Hardware QA checks (sensors, network, storage)
• Automating repetitive adb diagnostic steps in a workflow
• Getting a quick health snapshot of a connected device

Architecture

The project went through a refactoring (see Before / After below) that split a single flat script into a proper package:

DroidTest.py          ← entry point (backward-compatible launcher)
droidtest/
  __init__.py
  core.py             ← command loading and execution logic
  cli.py              ← argument parsing, output, banner
list.txt              ← default command list
tests/
  test_core.py        ← unit tests

This separation means the core logic (loading commands, running adb, collecting results) can be tested independently from the CLI behavior.

How It Works

Command loading (core.py)

Commands are read from a text file. Each line is an adb subcommand — the adb prefix is added automatically. Comments (#) and blank lines are skipped.

1
2
3
4

# This is a comment — ignored
shell getprop ro.product.model
shell dumpsys battery
shell wm size

1
2
3
4
5
6

def load_commands(file_path):
    for line in path.read_text().splitlines():
        line = line.strip()
        if not line or line.startswith("#"):
            continue
        commands.append(line)

Command execution

Each command is run via subprocess.run with shlex.split for safe argument handling. Results are captured as CommandResult dataclass instances with command, returncode, stdout, stderr, and an ok property.

1
2
3
4

completed = subprocess.run(
    ["adb"] + shlex.split(command),
    capture_output=True, text=True, timeout=timeout
)

shlex.split is important — it handles commands with quoted arguments correctly, where a naive .split() would break on spaces inside arguments.

Device targeting

If you have multiple devices connected, use --device to target a specific one:

1
2
3
4
5
6

adb devices
# List of devices attached
# R3CN90XXXXX    device
# emulator-5554  device

python DroidTest.py --device R3CN90XXXXX

This passes -s <serial> to every adb invocation.

Built-in Command Library

The OtherUsefulTests.txt file contains a reference list of over 60 documented adb test commands covering:

• Touchscreen, sensors (accelerometer, gyroscope, barometer, GPS, NFC, proximity, compass)
• Battery health, temperature, voltage, capacity
• Wi-Fi, Bluetooth, mobile data, network signal
• Storage read/write speed (dd benchmark)
• Camera, microphone, speaker, flashlight, vibration
• CPU frequency and temperature
• RAM, display resolution and density
• Security: root status, encryption state, security patch level
• Device info: model, manufacturer, serial, IMEI, Android version, kernel

CLI Options

JSON Report Format

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

{
  "summary": {
    "passed": 31,
    "failed": 3,
    "total": 34
  },
  "results": [
    {
      "command": "shell getprop ro.product.model",
      "returncode": 0,
      "stdout": "Pixel 6",
      "stderr": "",
      "ok": true
    },
    {
      "command": "shell dumpsys proximity",
      "returncode": 1,
      "stdout": "",
      "stderr": "No proximity sensor found",
      "ok": false
    }
  ]
}

Before / After

The original backup.py was a single-file script: argument parsing, execution, and output all in one function, with hard-coded command lists and no separation of concerns.

Connect Your Device

1. Enable Developer options — Settings → About phone → tap Build number 7 times
2. Enable USB debugging — Settings → Developer options → USB debugging
3. Connect via USB, accept the RSA key prompt on the phone
4. Verify: adb devices should show your device with device status

If the device shows unauthorized, revoke USB debugging authorizations on the device and reconnect. If nothing appears, try adb kill-server && adb start-server.

Running Tests

1

python -m unittest discover -s tests -p 'test_*.py'

Resources

• Android ADB documentation
• ADB shell commands reference
• Python subprocess module
• Python shlex module