u/Famous_Drive_9010

tauri-pilot: interactive testing CLI for Tauri v2 apps (Playwright alternative for WebKitGTK)
▲ 7 r/tauri

tauri-pilot: interactive testing CLI for Tauri v2 apps (Playwright alternative for WebKitGTK)

Hey everyone,

If you've ever attempted to automate UI testing on a Tauri app on Linux, you may have encountered the same obstacle: Playwright doesn't support WebKitGTK.

I built tauri-pilot to solve this. It's a lightweight CLI + plugin that lets you inspect, interact with, and debug your Tauri v2 app in real-time.

Setup is minimal:

# src-tauri/Cargo.toml
[dependencies]
tauri-plugin-pilot = { git = "https://github.com/mpiton/tauri-pilot" }

#[cfg(debug_assertions)]
{
    builder = builder.plugin(tauri_plugin_pilot::init());
}

Then from your terminal:

$ tauri-pilot ping
ok (3ms)

$ tauri-pilot snapshot -i
- heading "Settings" [ref=e1]
- textbox "API Key" [ref=e2] value=""
- button "Save" [ref=e3]

$ tauri-pilot fill @e2 "sk-test-123"
ok

$ tauri-pilot click @e3
ok

What you can do:

• Inspect the accessibility tree with element refs • Click, fill, type, press, select, check, scroll • Get element text/html/value/attributes • Capture screenshots • Wait for elements to appear/disappear • Execute arbitrary JS or call Tauri IPC commands • Capture console logs and network requests • Diff snapshots to see what changed

It's also designed to work with AI coding agents (Claude Code, etc.) the output format is optimized for LLM parsing.

The plugin runs only in debug builds, so there is zero overhead in production.

GitHub: https://github.com/mpiton/tauri-pilot License: MIT | Platform: Linux (macOS/Windows planned)

Curious to hear what the Tauri community thinks. What features would be most useful for your workflow?

u/Famous_Drive_9010 — 1 day ago