Amr Bashir 36b082a9c8 ci: pull `.crate` file from workspace `target` directory (#9732) 1 anno fa
..
src 36b082a9c8 ci: pull `.crate` file from workspace `target` directory (#9732) 1 anno fa
.gitignore 4b2aa35684 Add back WebDriver support (#2324) 4 anni fa
CHANGELOG.md 36b082a9c8 ci: pull `.crate` file from workspace `target` directory (#9732) 1 anno fa
Cargo.lock 36b082a9c8 ci: pull `.crate` file from workspace `target` directory (#9732) 1 anno fa
Cargo.toml 36b082a9c8 ci: pull `.crate` file from workspace `target` directory (#9732) 1 anno fa
LICENSE.spdx 4b2aa35684 Add back WebDriver support (#2324) 4 anni fa
LICENSE_APACHE-2.0 4b2aa35684 Add back WebDriver support (#2324) 4 anni fa
LICENSE_MIT 4b2aa35684 Add back WebDriver support (#2324) 4 anni fa
README.md 36b082a9c8 ci: pull `.crate` file from workspace `target` directory (#9732) 1 anno fa

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.app/docs/testing/webdriver/introduction, including a small example application with WebDriver tests.