Docs · Beta

Product documentation

What Lighthouse is, how to install and activate a beta key, and how to inspect · record · play on Windows and Android. For a short walkthrough see the user guide; for edge cases see FAQ and limits.

Overview

Lighthouse Tests Suite is a Windows desktop app for UI test automation. Attach to a running Windows process (UIA) or an Android device/emulator (Appium), inspect a live visual map, record steps, and play them back.

Credo: write once, test everywhere — give controls a shared AutomationId (Flutter, .NET MAUI, and similar stacks) so the same suite can run on Windows and Android. iOS is not available yet.

  • Inspect — tree + screenshot map with overlays and properties
  • Record — clicks, text, asserts, waits (platform-specific extras on Android)
  • Play — run a test or the whole suite; review results on the Dashboard

Install

  1. Download the Windows Setup from the home page when the Download button is enabled.
  2. If SmartScreen appears: More info → Run anyway (unsigned beta).
  3. Framework-dependent builds need the .NET 10 Desktop Runtime unless you have a self-contained (R2) build — the download hint on the home page says which you have.
  4. Open Lighthouse Tests Suite from the Start menu.

Requirements: Windows 10/11 x64. No Visual Studio required for Setup users.

Beta license

Installed Setup builds auto-activate a free 30-day device trial on first launch. No key paste is required for that first period. Remaining time appears in Settings → Beta license (“Free beta — N days left”).

  1. Install and open Lighthouse — Workspace unlocks for the free trial.
  2. When the free period ends, an activation panel asks for a renewal key.
  3. Request a key via Contact, paste it (starts with LH1.), and choose Activate.
  • Reinstalling or clearing only one local store does not mint a new free trial on the same PC.
  • Issued renewal keys are bound to this PC/user and expire after the issued window (usually 30 days).
  • Entitlement is stored under LocalAppData, ProgramData, and HKCU (DPAPI-protected).
  • Developer / unpackaged runs bypass the gate with LIGHTHOUSE_LICENSING=0 — not for public Setup.

Workspace layout

The main window has three columns:

  • Tests — suite list, search, new/rename/delete
  • Test — steps, script panel, Run / Export, run console
  • Inspector — visual map, recording toolbar, element properties

Use the header to switch Platform (Windows UIA / Android), pick an application or device, and open Dashboard or Settings.

Windows workflow

  1. Platform → Windows UIA.
  2. Choose the target process from Application (refresh if it just started).
  3. Create or select a test → Start Recording → interact with the target app.
  4. Right-click the map (or use Actions) for Enter Text, asserts, and waits.
  5. Run Test to replay. Prefer elements with a stable AutomationId or name.

Elevation: if attach fails against an Administrator app, run Lighthouse elevated or run the target without elevation. See limits.

Android workflow

  1. Install adb (platform-tools) and Appium 2 with the uiautomator2 driver.
  2. Platform → Android → pick device → optional package → Connect.
  3. Start Recording, then left-click the Inspector map (device follows). Live taps via adb and EnterText from focused fields may also record when available.
  4. Use toolbar actions for Back / Swipe when needed.
  5. Run Test uses Android playback (Click, EnterText, Assert, Wait, Delay, Back, Swipe, screenshots when supported).

Refresh Inspector after navigation if the map looks stale; live hierarchy watch also refreshes when connected.

AutomationId & portability

Steps with an AutomationId can resolve on Android by id only (no Windows class/bounds fallthrough). That is the contract for portable Flutter / MAUI suites.

  • Set the same id in shared UI code on each platform.
  • Use Import / Check portability in the app when moving a suite between Windows and Android.
  • Screenshots, DragDrop, and some Windows-only or Android-only steps stay platform-specific.

Updates

Installed Setup builds can check for updates from Settings → Check for updates… when a public feed is configured. Force / minimum-version policies may block Workspace until you update.

Unpackaged dotnet run builds do not self-update.

Data & logs

  • Tests: %LocalAppData%\Lighthouse.Tests.Suite\apps\
  • Beta license activation: under the same LocalAppData folder (sealed)
  • Logs: %LocalAppData%\Lighthouse.Tests.Suite\logs\

Nothing in those folders is uploaded unless you choose to send feedback. See Privacy.

Beta Download Quick start guide