Integration tests

• Download the drivers using the compiled executable and print out the driver version
• Use https://github.com/stevepryde/thirtyfour in a test using a driver downloaded with webdriver-install

Unit tests

• geckodriver::direct_download_url seems testable
• geckodriver::latest_version could be tested with mockito

called `Result::unwrap()` on an `Err` value: No support for unarchiving %3C, yet

It looks the the way to fetch chromedriver versions has changed

The powershell command doesn't seem to work: https://github.com/phansch/webdriver-install/actions/runs/535042693/workflow#L71

That should significantly reduce waiting time for PRs (~2 minutes currently)

Installation of drivers should work without problems on WSL.

See https://firefox-source-docs.mozilla.org/testing/geckodriver/Support.html

According to mozilla/geckodriver#1670 (comment), newer geckodriver releases may not work correctly on older Firefox versions, so we need to be sure to install the correct geckodriver release.

Probably have to maintain this mapping manually until there is something like LATEST_RELEASE for chromedriver.

This issue is about making webdriver-install compile and run on Windows 10. It is not about adding support for iedriver or edgedriver

Cross compilation

See https://stackoverflow.com/a/62853319/6830113

rustup target add x86_64-pc-windows-gnu
rustup toolchain install stable-x86_64-pc-windows-gnu
sudo apt-get install gcc-mingw-w64-x86-64 -y
cargo test --target x86_64-pc-windows-gnu

VM Development / Testing

I haven't used windows in a long time, but if I understand everything correctly..

• I can get my Windows 10 product key via sudo acpidump -n MSDM
• Using that key, I should be able to set up a qemu VM (See this blog post), thus avoiding the mess of VirtualBox and vagrant
• The Windows 10 .iso can be downloaded here
• With the above steps done, it should just be a simple VM setup. Inside the VM I'd setup my own dev environment for webdriver-install
• Need to add windows to the CI setup as well

Would really appreciate an option for that.

• How to install the correct chromedriver version: https://chromedriver.chromium.org/downloads/version-selection
• wasm-pack also installs various drivers for their test command, but code seems outdated? https://github.com/rustwasm/wasm-pack/tree/master/src/test/webdriver
• Ruby's webdrivers gem seems to be the best out there? https://github.com/titusfortner/webdrivers/tree/master/lib
• Popular Java version: https://github.com/bonigarcia/webdrivermanager

• docs.rs
• crates.io
• minimum rust version

I think this might be a more convenient API than the current one:

Driver::Gecko.install();
Driver::Gecko.install_version(version);
Driver::Gecko.install_into(dir);
Driver::Gecko.update();
Driver::Gecko.remove();
Driver::Gecko.info();

This requires less argument passing and only one import of the enum.

I need to figure out how to publish this both as a library and a binary installable via cargo install.

The integration tests should:

1. Install the driver into /tmp, using installer::install(driver)
2. Run driver --version and make sure the return status is 0
3. Remove the installed driver again

Once webdriver-install has a solid API, we need to have documentation that shows how to use it with other tools:

• Different CI platforms
• https://github.com/rustwasm/wasm-pack
  • They have their own webdriver setup: https://github.com/rustwasm/wasm-pack/tree/master/src/test/webdriver but that wasn't updated in over a year.
• https://github.com/stevepryde/thirtyfour