Drive an installed Tauri desktop app's UI end-to-end using a WebDriver client
domain: v2.tauri.app · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For the officially documented path, use WebdriverIO with @wdio/tauri-service, which supports Windows, Linux, and macOS
Scaffold a project with npm create wdio@latest, choose Desktop Testing / Tauri, and set the built app's binary path in the config
By default the service runs an embedded WebDriver server inside the app rather than requiring an external driver process, which is how macOS support is achieved
For custom harnesses or plain Selenium clients, drive tauri-driver directly as a standalone WebDriver server instead of using the WebdriverIO service
Point a standard WebDriver/Selenium client at the driver's local endpoint and interact with the app like a browser session
Known gotchas
Driving tauri-driver directly supports Windows and Linux only — there is no equivalent standalone WKWebView driver for macOS; macOS requires the WebdriverIO embedded-server path or a third-party fork
This targets CI/test automation of an app you built and control, not remote automation of arbitrary third-party installed apps
It requires a local built app binary with an explicitly configured path, unlike Selenium+chromedriver pointed at any web page
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?