Skip to main content
The Test Editor is where you build, execute, and debug your tests. It provides a visual interface to add test steps, run them on real devices, and monitor execution in real-time. Test Editor Interface

Overview

The Test Editor consists of four main areas:
  1. Device Screen (left) - Live view of the device running your test
  2. Editor Panel (center) - Where you build your test with steps
  3. Device Logs (bottom right) - Real-time system logs from the device
  4. Test Controls (top) - Run, save, and configure your test

Opening the Test Editor

To open the Test Editor:
  1. Go to Test Suite in the sidebar
  2. Click on any test in the list
  3. Click Open Editor button
Alternatively, create a new test and you’ll be taken directly to the editor.

Editor Tabs

The editor has three tabs:

Editor Tab

The visual step builder where you create your test by adding blocks. Test Steps Step Types (see Step Types):
  • 🗣️ Instruction - AI-powered actions (tap, type, swipe)
  • ☑️ Validation - Check conditions and assertions
  • ⚙️ Explicit - Precise click/type actions with selectors
  • 💻 Script - Custom code execution
  • Manual - Wait, open/close app, go home, set location, open deep links
  • 🔁 Loop - Repeat actions multiple times
  • 🔀 Decision - Conditional branching
  • Help - Documentation and examples

YAML Tab

View and edit the YAML representation of your test. You can export this for CI/CD integration. YAML View Actions:
  • Download - Save YAML file locally
  • Edit - Manually edit the YAML (advanced)

Variables Tab

Create and manage test variables for dynamic data. Variables Tab Variables are referenced in steps using {{ variable_name }} syntax.

Adding Steps

To add a step:
  1. Click or drag in any step type button at the bottom of the editor
  2. The step is added to your test sequence
  3. Fill in the step description or configuration
Instruction Step

Step Interactions

Step Hover Actions Hover over any step to reveal quick actions:
  • ▶ Run - Execute this single step on the device
  • 📋 Duplicate - Copy the step with all settings
  • 🗑️ Delete - Remove the step from the test
Reorder Steps: Drag the step handle (⋮⋮) to move steps up or down in the sequence. Multi-Select: Click and drag across multiple steps to select them, then delete or move them together. Multiple Steps in Editor

Device Connection

When you open the Test Editor, a device automatically starts connecting:
  1. Connecting… - Device is booting (iOS: 5-30 seconds, Android: 5-45 seconds — varies by app size)
  2. Connected - Device is ready, live screen visible
  3. Running - Test or test steps executing on the device
Device Panel with Stop Button Device Panel:
  • Shows device model and OS version at the top
  • Stop device button (red) - Disconnect the device when done
  • Live device screen updates in real-time during test execution

Running Tests

To run your test:
  1. Ensure device is connected (live screen visible)
  2. Click Run Steps button in the top right
  3. Watch execution in real-time on the device screen
  4. Check Device Logs for system output
  5. Review results when complete
Test running - step highlighted with spinner During execution, the active step is highlighted in purple with a loading spinner. Once complete, each step displays its result status. Test completed showing pass/fail results

Test Controls

Top toolbar buttons:
  • Notification Bell - Get browser notifications when a device is done booting or steps complete (ensure your browser has permissions!)
  • Settings - Configure test options
  • History - View past test runs
  • Run Steps - Execute all steps
Device info:
  • Device: Selected device model
  • Runtime: OS version
  • Build: Associated app build
  • Steps: Current step count

Device Logs

The Device Logs panel shows real-time system output:
  • Application logs
  • System messages
  • Error output
  • Execution events
Click Clear console logs to reset the log view.

Best Practices

  1. Start simple - Add one step at a time and test
  2. Use validations - Verify expected outcomes after actions
  3. Describe steps clearly - Descriptive text helps debugging
  4. Check device logs - Look for errors during execution

Next Steps


Need help? Contact [email protected]