auto-drive-tauri

Automate Tauri desktop app testing by integrating a WebDriver or WebSocket bridge to drive DOM interactions and verify end-to-end rendering. This approach streamlines regression testing workflows after code changes.

WebDriver drives the Tauri webview's DOM for rendering and interaction assertions, while a WebSocket bridge provides deterministic, headless app interaction. Both methods automate end-to-end testing but offer different connection mechanisms.

Yes, running automated tests on a Tauri application requires a local model server. You also need a running Tauri app instance and an active WebDriver or WebSocket connection to execute the verification successfully.

Verify end-to-end changes in a Tauri app by triggering automated tests through the skill's command interface. The system uses WebDriver or WebSocket integration to assert the application behaves as expected following the code updates.

Yes, you can use WebDriver for headless interaction testing with a Tauri webview. Alternatively, the WebSocket bridge specifically supports deterministic, headless app interaction for continuous integration workflows and regression testing.

Tauri test automation fails without a running app instance because the WebDriver or WebSocket bridge requires an active application target to connect to and execute DOM interactions or end-to-end verifications.