chip 50d135b20f fix documentation link in tauri-driver readme (#3819) 3 lat temu
..
src cd9dfc7b9a fix(driver): expose native-host option and set default to 127.0.0.1 (#3816) 3 lat temu
.gitignore 4b2aa35684 Add back WebDriver support (#2324) 4 lat temu
.license_template 4b2aa35684 Add back WebDriver support (#2324) 4 lat temu
CHANGELOG.md 3b69596742 Apply Version Updates From Current Changes (#3803) 3 lat temu
Cargo.lock c59846d088 chore(webdriver): update lockfile 3 lat temu
Cargo.toml 3b69596742 Apply Version Updates From Current Changes (#3803) 3 lat temu
LICENSE.spdx 4b2aa35684 Add back WebDriver support (#2324) 4 lat temu
LICENSE_APACHE-2.0 4b2aa35684 Add back WebDriver support (#2324) 4 lat temu
LICENSE_MIT 4b2aa35684 Add back WebDriver support (#2324) 4 lat temu
README.md 50d135b20f fix documentation link in tauri-driver readme (#3819) 3 lat temu

README.md

tauri-driver (pre-alpha)

Cross-platform WebDriver server for Tauri applications.

This is a WebDriver Intermediary Node that wraps the native WebDriver server for platforms that Tauri supports. Your WebDriver client will connect to the running tauri-driver server, and tauri-driver will handle starting the native WebDriver server for you behind the scenes. It requires two separate ports to be used since two distinct WebDriver Remote Ends run.

You can configure the ports used with arguments when starting the binary:

  • --port (default: 4444)
  • --native-port (default: 4445)

Supported platforms:

note: the (probably) items haven't been proof-of-concept'd yet, and if it is not possible to use the listed native webdriver, then a custom implementation will be used that wraps around wry.

Trying it out

Check out the documentation at https://tauri.studio/docs/testing/webdriver/introduction, including a small example application with WebDriver tests.