tauri/tooling/webdriver
Lucas Fernandes Nogueira 0f1558980a
fix(core): docs.rs on Windows and macOS (#3566)
Co-authored-by: chip <chip@chip.sh>
2022-03-02 13:08:42 -03:00
..
src feat(driver): add `args` to `tauri:options` (#3154) 2022-01-03 17:37:16 -03:00
.gitignore Add back WebDriver support (#2324) 2021-08-01 23:54:10 -03:00
.license_template Add back WebDriver support (#2324) 2021-08-01 23:54:10 -03:00
CHANGELOG.md Apply Version Updates From Current Changes (#2522) 2022-02-10 18:03:25 -03:00
Cargo.lock fix(core): docs.rs on Windows and macOS (#3566) 2022-03-02 13:08:42 -03:00
Cargo.toml Apply Version Updates From Current Changes (#2522) 2022-02-10 18:03:25 -03:00
LICENSE.spdx Add back WebDriver support (#2324) 2021-08-01 23:54:10 -03:00
LICENSE_APACHE-2.0 Add back WebDriver support (#2324) 2021-08-01 23:54:10 -03:00
LICENSE_MIT Add back WebDriver support (#2324) 2021-08-01 23:54:10 -03:00
README.md Restructure docs (#3180) 2022-01-07 09:30:23 -03:00

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/en/docs/guides/webdriver/ci to build a small example application that had WebDriver tests.