anchor.diff:  [DEBUG] Detecting chrome version using online commands.properties
   [DEBUG] Running command on the shell: [google-chrome, --version]
   [DEBUG] Result: Google Chrome 92.0.4515.107
  -[DEBUG] Latest version of chromedriver according to https://chromedriver.storage.googleapis.com/LATEST_RELEASE_92 is 92.0.4515.107
  +[DEBUG] Latest version of chromedriver, according to https://chromedriver.storage.googleapis.com/LATEST_RELEASE_92 is 92.0.4515.107
   [INFO] Using chromedriver 92.0.4515.107 (resolved driver for Chrome 92)
   [INFO] Reading https://chromedriver.storage.googleapis.com/ to seek chromedriver
   [DEBUG] Driver to be downloaded chromedriver 92.0.4515.107
  
positive.code: To configure the WebDriverManager Agent, we need to specify the path of the WebDriverManager https://github.com/bonigarcia/webdrivermanager/releases/download/webdrivermanager-{project-version}/webdrivermanager-{project-version}-fat.jar[fat-JAR] using the JVM flag `-javaagent:/path/to/webdrivermanager-{project-version}-fat.jar`. Alternatively, it can be done using Maven (see a complete project example https://github.com/bonigarcia/wdm-agent-example/[here]).
  
  === Selenium-Jupiter
  WebDriverManager is the heart of the project https://github.com/bonigarcia/selenium-jupiter[Selenium-Jupiter], an open-source JUnit 5 extension for Selenium WebDriver. Selenium-Jupiter uses the programming and extension model provided by JUnit 5 (named https://junit.org/junit5/docs/current/user-guide/[Jupiter]) together with WebDriverManager to create tests with reduced boilerplate code. For instance, thanks to the Jupiter feature for parameter resolution, we can declare a type of the `WebDriver` hierarchy (e.g., `ChromeDriver`) as a test parameter. Internally, Selenium-Jupiter resolves its driver and creates the instance before tests, and then, the browser is gracefully closed at the end of the test. For example:
  
  [source,java]
  ----
  
negative.code: ----
  
  === WebDriverManager Server
  The WebDriverManager Server is based on HTTP and offers two types of services. First, it can resolve drivers (chromedriver, geckodriver, etc.). The WebDriverManager Server exposes a simple REST-like API to this aim. WebDriverManager Server sends the resolved driver as an HTTP attachment in the response. The endpoints provided by this API are the following (supposing that WebDriverManager is running the localhost in its default port, i.e., 4444):
  
  * http://localhost:4444/chromedriver[http://localhost:4444/chromedriver]: To resolve chromedriver.
  * http://localhost:4444/firefoxdriver[http://localhost:4444/firefoxdriver]: To resolve geckodriver.
  