chrome-for-testing-manager
Programmatic management of chrome-for-testing installations.
- Automatically resolves the configured Chrome for Testing version.
- Automatically downloads chrome-for-testing
chromeandchromedriverbinaries into a local cache directory. - Possibility to spawn the chromedriver process using a random port.
- Optional line-based listener for chromedriver stdout/stderr during a run.
- Built-int session management.
Frees you from the need to
- manually download a chromedriver package matching your locally installed chrome,
- starting and stopping it manually,
- hardcoding the chosen chromedriver port into your tests and
- doing this all-over when trying to test with a new version of chrome.
Installation
[]
= "0.9"
= "0.12"
= "0.36"
# Additional dependencies for the example below.
= "0.5"
= { = "1", = ["full"] }
Example
use *;
use ;
use Report;
use Duration;
use *;
// This library requires being used in a multithreaded runtime.
// If you want to run a test, use: `#[tokio::test(flavor = "multi_thread")]`.
async
Managed sessions opt-out
The with_session function. providing a thirtyfour session, called in the example, was only available because
chrome-for-testing-manager enables its thirtyfour feature by default.
If you just want it's chrome/chromedriver version resolution, download and launch orchestration, declare the dependency as
= { = "0.9", = false }
instead.
MSRV
- Starting from version
0.8.0, the minimum supported rust version is1.89.0 - Starting from version
0.7.0, the minimum supported rust version is1.85.1 - Starting from version
0.5.0, the minimum supported rust version is1.85.0 - Starting from version
0.1.0, the minimum supported rust version is1.81.0