36eee37220
* Restructure the repository * lock file * fmt * fix bench * fix cli template test * remove accidental file * fix mv command * clippy * upgrade paths-filter github action * fix cli migration tests * lockfile * license headers * clippy * scope test-core to tauri crate * license header * correct --manifest-path usage * lockfile * fix tauri-driver on macOS [skip ci] * build target ios * try downgrade env_logger * downgrade 0.1.7 * try to fix bench * bench overflow * revert overflow fix, fix tauri_root_path * revert env_logger downgrade * fmt * raise msrv to 1.71 * fmt * delete .cargo/config.toml [skip ci] --------- Co-authored-by: Lucas Nogueira <lucas@tauri.app> |
||
---|---|---|
.. | ||
src | ||
Cargo.toml | ||
CHANGELOG.md | ||
LICENSE_APACHE-2.0 | ||
LICENSE_MIT | ||
LICENSE.spdx | ||
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:
- [pre-alpha] Linux w/
WebKitWebDriver
- [pre-alpha] Windows w/ Microsoft Edge Driver
- [Todo] macOS w/ Appium Mac2 Driver (probably)
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.