Glossary
Key terms and definitions used in device testing and automation
25 terms
AI Agent
An autonomous AI system that can perform tasks on devices without human intervention.
AI Agents are autonomous software systems powered by large language models (LLMs) like Claude that can interact with applications and devices. In device testing, AI agents can navigate UIs, fill forms, validate screens, and execute complex test scenarios using natural language instructions instead of scripted code. RobotActions supports AI agent integration via MCP (Model Context Protocol).
Appium
An open-source framework for automating mobile app testing on real devices and emulators.
Appium is the industry-standard open-source test automation framework for mobile applications. It supports native, hybrid, and mobile web apps on iOS and Android. Appium uses the WebDriver protocol, allowing you to write tests in any language (Java, Python, JavaScript, etc.). RobotActions provides cloud-hosted Appium servers connected to real devices, eliminating the need for local device management.
Browser Grid
A cluster of machines running different browsers for parallel cross-browser testing.
A Browser Grid (often called Selenium Grid) distributes test execution across multiple machines, each running different browser and OS combinations. This enables parallel cross-browser testing, dramatically reducing total test time. RobotActions provides a managed browser grid with Chrome, Firefox, Safari, and Edge across Windows, macOS, and Linux.
CI/CD
Continuous Integration and Continuous Delivery — automated pipelines that build, test, and deploy code.
CI/CD (Continuous Integration / Continuous Delivery) is a software development practice where code changes are automatically built, tested, and prepared for release. In device testing, CI/CD pipelines trigger automated test suites on real devices whenever code is pushed. RobotActions integrates with Jenkins, GitHub Actions, GitLab CI, and other CI/CD tools to run device tests as part of your deployment pipeline.
Claude
Anthropic's AI assistant that can control real devices via MCP integration.
Claude is a large language model created by Anthropic. Through MCP (Model Context Protocol) integration with RobotActions, Claude can directly interact with real Android and iOS devices — tapping buttons, typing text, taking screenshots, and running test scenarios using natural language commands. Claude Desktop and Claude Code can both connect to RobotActions device farm.
Cross-Browser Testing
Verifying that a web application works correctly across different browsers and versions.
Cross-browser testing ensures your web application renders and functions consistently across different browsers (Chrome, Firefox, Safari, Edge) and their versions. This is critical because browsers interpret HTML, CSS, and JavaScript differently. RobotActions provides a browser grid with multiple browser/OS combinations for automated and manual cross-browser testing.
Cursor
An AI-powered code editor that can connect to RobotActions for device testing via MCP.
Cursor is an AI-first code editor built on VS Code. Through MCP integration, Cursor can connect to RobotActions' device farm, allowing developers to control real devices directly from their IDE. This enables AI-assisted test writing, debugging on real devices, and interactive device exploration — all without leaving the editor.
Desired Capabilities
Key-value pairs that tell the automation server what kind of device and session you want.
Desired Capabilities (or simply 'capabilities') are a set of key-value pairs sent to an Appium or Selenium server to specify the test environment. They define the target platform (Android/iOS), device name, browser, app path, automation engine, and other session parameters. In RobotActions, capabilities are used to request specific devices from the cloud farm, e.g., { platformName: 'Android', deviceName: 'Pixel 8', automationName: 'UiAutomator2' }.
Device Farm
A cloud-hosted collection of real mobile devices available for remote testing.
A device farm is a managed infrastructure of real physical devices (smartphones, tablets) accessible remotely over the internet. Instead of purchasing and maintaining hundreds of devices locally /* brand-ok: defines the category */, teams connect to a device farm to run manual and automated tests on real hardware. RobotActions operates a cloud device farm with Android and iOS devices, providing browser-based access via low-latency live streaming.
Emulator vs Simulator vs Real Device
Three approaches to testing: emulated hardware, simulated OS, or actual physical devices.
An emulator (Android) mimics both hardware and software of a device, running a full OS image. A simulator (iOS) only simulates the software environment without hardware emulation. Real devices are actual physical phones/tablets. While emulators and simulators are useful for development, they can miss hardware-specific bugs (GPS, camera, Bluetooth, performance). RobotActions provides real device testing to catch issues that emulators and simulators miss.
GitHub Actions
GitHub's built-in CI/CD platform for automating workflows directly from your repository.
GitHub Actions is a CI/CD and automation platform integrated into GitHub. It allows you to create workflows triggered by events like push, pull request, or schedule. For device testing, you can configure GitHub Actions workflows to automatically run your Appium or Selenium tests on RobotActions' device farm whenever code changes are pushed, ensuring continuous quality validation.
H.264
A video compression standard used for efficient real-time device screen streaming.
H.264 (also known as AVC) is a widely-used video compression standard that provides high-quality video at low bitrates. In remote device testing, H.264 encoding is used to stream the device screen to the user's browser with minimal latency and bandwidth usage. RobotActions uses H.264 streaming alongside MJPEG to deliver smooth, real-time device interaction over the internet.
Headless Browser
A browser that runs without a visible UI, used for faster automated testing.
A headless browser is a web browser without a graphical user interface. It executes web pages and JavaScript just like a regular browser, but renders nothing on screen. Headless mode (available in Chrome, Firefox, and others) is commonly used in CI/CD pipelines for faster automated testing since it doesn't need GPU rendering. However, headless tests may miss visual rendering bugs that only appear in headed mode.
Hub and Node
Selenium Grid architecture where a Hub routes tests to Node machines running browsers.
In Selenium Grid, the Hub is the central server that receives test requests and routes them to available Nodes. Nodes are machines registered with the Hub, each running one or more browser instances. When a test creates a new session, the Hub finds a matching Node based on requested capabilities and forwards the session. RobotActions manages Hub and Node infrastructure so teams don't have to maintain their own grid.
Jenkins Pipeline
A Jenkins CI/CD workflow defined as code for building, testing, and deploying applications.
Jenkins Pipeline is a suite of plugins that supports defining continuous delivery pipelines as code (Jenkinsfile). Pipelines can include stages for building, running unit tests, deploying to staging, and executing device tests. RobotActions provides Jenkins plugins and API endpoints to integrate cloud device testing into your Jenkins Pipeline stages.
MCP (Model Context Protocol)
An open protocol that lets AI agents interact with external tools and services like device farms.
MCP (Model Context Protocol) is an open standard created by Anthropic that enables AI models to interact with external tools and data sources. In the context of RobotActions, MCP allows AI agents (Claude, Cursor, etc.) to control real mobile devices — tapping, swiping, typing, taking screenshots, and running test scenarios — all through natural language commands. This bridges the gap between AI assistants and physical device testing.
MJPEG
Motion JPEG — a video format that streams individual JPEG frames for device screen viewing.
MJPEG (Motion JPEG) is a video compression format where each frame is independently compressed as a JPEG image. In device testing, MJPEG streaming is used to display the remote device's screen in a web browser. While less efficient than H.264, MJPEG is simpler to implement and works without special codec support. RobotActions uses MJPEG as a fallback streaming option alongside H.264.
Playwright
A modern browser automation framework by Microsoft for end-to-end web testing.
Playwright is an open-source browser automation library developed by Microsoft. It supports Chromium, Firefox, and WebKit with a single API, offering features like auto-waiting, network interception, and mobile emulation. Unlike Selenium, Playwright communicates with browsers via the Chrome DevTools Protocol (CDP) for faster and more reliable automation. RobotActions integrates with Playwright for cross-browser testing on real infrastructure.
Real Device Testing
Running tests on actual physical devices rather than emulators or simulators.
Real device testing means executing automated or manual tests on actual physical smartphones and tablets. This provides the most accurate results because real devices have actual hardware (cameras, GPS, Bluetooth, NFC), real performance characteristics, and genuine OS behavior. Issues like touch responsiveness, battery drain, memory pressure, and carrier-specific behavior can only be caught on real devices. RobotActions provides a cloud farm of real devices for this purpose.
Selenium
The most widely-used open-source framework for automating web browser testing.
Selenium is an open-source browser automation framework that has been the industry standard for web testing since 2004. Selenium WebDriver provides a programming interface to create and execute test scripts across browsers. Selenium Grid enables parallel test execution on multiple machines. RobotActions provides managed Selenium Grid infrastructure with real browsers on real machines, eliminating setup and maintenance overhead.
Session
A connection between your test script and a specific device or browser instance.
In test automation, a session represents an active connection between your test client and a remote device or browser. When you create a new WebDriver session with desired capabilities, the server allocates a matching device/browser and returns a session ID. All subsequent commands (tap, type, navigate) are sent to that session. Sessions have timeouts and are cleaned up after tests complete. RobotActions manages session allocation, queuing, and cleanup automatically.
VNC
Virtual Network Computing — a protocol for remote desktop access to devices.
VNC (Virtual Network Computing) is a graphical desktop-sharing protocol that transmits keyboard and mouse input to a remote machine and receives screen updates back. In device testing, VNC-like protocols enable interactive remote control of devices. While traditional VNC can be high-latency, modern implementations optimize for speed. RobotActions uses optimized low-latency streaming protocols that provide VNC-like functionality with better performance.
WebDriver
A W3C standard protocol for browser and device automation used by Selenium and Appium.
WebDriver is a W3C standard that defines a platform-neutral interface for controlling web browsers and mobile devices. It provides a REST API that test frameworks use to send commands (navigate, click, type, find elements) to a remote browser or device. Both Selenium (for web) and Appium (for mobile) implement the WebDriver protocol. RobotActions' cloud infrastructure speaks WebDriver natively, making it compatible with any WebDriver-based test framework.
WebDriverIO
A JavaScript/TypeScript test automation framework built on the WebDriver protocol.
WebDriverIO (WDIO) is a popular JavaScript/TypeScript test automation framework. It provides a concise API for browser and mobile testing, built on top of the WebDriver and Chrome DevTools protocols. WDIO includes a test runner, assertion library, and rich plugin ecosystem. It works with Selenium Grid and Appium, making it fully compatible with RobotActions' cloud device farm for both web and mobile testing.
WebRTC
A real-time communication protocol enabling low-latency audio/video streaming in browsers.
WebRTC (Web Real-Time Communication) is a set of protocols and APIs that enable real-time audio, video, and data communication directly between browsers. In device testing, WebRTC can be used for ultra-low-latency device screen streaming, providing near-instant visual feedback when interacting with remote devices. WebRTC's peer-to-peer architecture minimizes latency compared to server-relayed streaming methods.