Robot Runner is a modern, cross-platform GUI tool designed to simplify test automation workflows using Robot Framework and Appium. Built with Tauri v2, React, and TypeScript, it provides a native, efficient experience for QA engineers and developers working on Android automation.
Key Features:
Device Management: Supports ADB device detection, wireless connection via pairing code (Android 11+), remote access via ngrok, and device diagnostics.
Test Execution: Offers flexible modes including file-based execution, folder runs, and argument files. Includes a smart automation root for path resolution and live logs viewing.
Advanced Tools: Features configuration profiles, a powerful UI Inspector, screen mirroring powered by scrcpy, and performance monitoring with data export capabilities.
History & Reports: Provides access to past test runs, re-run capabilities, and integrated logcat viewer with filtering.
Audience & Benefit:
Ideal for QA engineers, developers, and automation testers seeking a streamlined approach to managing Android automation projects. Robot Runner enhances efficiency by consolidating essential tools into a single interface, reducing manual setup, and improving test execution workflows.
The application can be installed via winget on Windows using winget install lucasdeeiroz.RobotRunner.
README
Robot Runner
Robot Runner is a modern, high-performance desktop application designed to streamline Android automation with Robot Framework and Appium. Built with Tauri v2, React, and TypeScript, it offers a native, resource-efficient experience for QA engineers and developers.
š Key Features
š± Device Management
ADB Devices Detection: Detects Android devices connected via USB or Wi-Fi.
Remote Access: Full support for remote devices via ngrok tunneling.
Device Diagnostics: Built-in toolbox to analyze app/system performance, get app/system logs, and send ADB commands to the device.
ā” Test Execution
Flexible Running Modes:
File Mode: Select and run individual .robot files.
Folder Mode: Execute all tests within a specific directory.
Argument Files: Run complex test suites defined in .args or .txt files.
Smart Automation Root: Define a specific working directory ("Automation Root") to resolve relative paths correctly in your argument files.
Live Logs: View Appium and Robot Framework logs in real-time within the app.
š ļø Advanced Tools
Configuration Profiles: Create and switch between multiple configuration profiles (e.g., "Work Project", "App B", "Personal Project") to manage different path setups and settings instantly.
Inspector: A powerful UI Inspector to visualize, select and copy locators from elements.
Screen Mirroring: Embedded high-performance screen mirroring powered by scrcpy (works over USB and Wi-Fi).
Performance Monitoring: Track CPU, RAM, and Battery usage of your device in real-time and export session data to CSV.
š History & Reports
Historical Logs: Access past test runs, grouped by Date, Device, or .
.dmg: Standard disk image installer. Drag to Applications.
.app.tar.gz: Compressed application bundle.
āļø Configuring Your Automation Project
To use Robot Runner with your project, you need to configure the paths in the Settings tab.
1. Project Structure
Robot Runner works best with a standard Robot Framework structure. Recommended structure:
my-automation-project/ # Your Automation Root
āāā suites/ # Your .robot test files
āāā resources/ # Resource files (.resource, .py, variables)
āāā args/ # Argument files for complex runs
āāā results/ # Output directory (handled by Runner)
2. Setting Up Paths
Go to Settings > Paths and configure:
Suites Directory: Point to your suites/ folder. This is where the File Explorer will open by default.
Automation Root (Optional): If your project uses relative paths (e.g., Resource ../resources/common.robot), set this to your project's root folder (my-automation-project/). This ensures all imports resolve correctly during execution.
3. Appium Configuration
Ensure Appium is installed (npm install -g appium).
In Settings > Appium, configure the Host (default: 127.0.0.1) and Port (default: 4723).
Robot Runner will attempt to automaticall start Appium if it's not running.
If you use a custom Appium configuration, you can set arguments in the Appium Arguments field.
4. Running Tests
Go to the Run tab.
Select your target Device.
Choose your mode:
File: Browse and select a .robot file.
Folder: Select a folder to run all tests inside it.
Args: Select an argument file to run a specific configuration.
Click Run.
5. History
Go to History tab to view past test runs. You can:
View Logs: View the logs for any test run.
View Report: View the report for any test run.
Organize: Organize your test runs by date, device, or OS version.
š ļø Prerequisites
Node.js (v18+) & npm
Python (3.8+) with robotframework and robotframework-appiumlibrary installed.