Closed charleslowell-valstro closed 1 week ago
It looks like you have msedgedriver in your PATH based on your second command (and as always probably check if it's the right version).
unknown error: no msedge binary
means that the binary
field that msedgedriver expects to run was not able to be found. That binary field is taken from tauri:options > application
, so whatever is set there is what it looks for. That example repository has the WebDriver examples 2 sub-directories deep from the root of the repo which is where target
gets built. Likely, the parent directories are not aligned with wherever you have your WebDriver JavaScript snippet at when you assign const appexe
.
Sidenote: if you want to run cargo tauri
commands then you need to install the subcommand first with cargo install tauri-cli
.
@chippers Thanks! It was totally the path. I was not running the tauri-driver in the same directory as I was running the node script. That got me working on the hello_tauri app, and so I'm going to close this issue.
However, one thing I noticed is that when I apply it to my own app, I'm running into trouble because it is a multi window app, and there does not appear to be away to interact with multiple windows from webdriver. Is there any trails to follow around using tauri-driver with multi-window apps?
Describe the bug
I'm trying to just use raw webdriver (not selenium, and not @wdio) using tauri-driver on Windows, using the demonstration app at https://github.com/chippers/hello_tauri
However, whenever I try to create a session, it fails with the following error:
Reproduction
Only local connections are allowed. Please see https://aka.ms/WebDriverSecurity for suggestions on keeping Microsoft Edge WebDriver safe.
Microsoft Edge WebDriver was started successfully.
Expected behavior
I'd expect a webdriver session to be created.
Full
tauri info
outputStack trace
Additional context
No response