anchor.diff:  
   * Fat-JAR:
   
  +[source,shell,subs="attributes+"]
  +----
  +java -jar webdrivermanager-{project-version}-fat.jar runInDocker chrome
  +----
  +
  +* Source code:
  +
   [source,shell]
   ----
  -java -jar webdrivermanager-5.0.0-fat.jar runInDocker chrome
  -----
  -
  -* Source code:
  -
  -[source,shell]
  -----
   mvn exec:java -Dexec.args="runInDocker chrome"
   ----
   
   * Docker container:
   
  -[source,shell]
  -----
  -docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome 91" bonigarcia/webdrivermanager:5.0.0
  +[source,shell,subs="attributes+"]
  +----
  +docker run --rm -it -v /var/run/docker.sock:/var/run/docker.sock -e ARGS="runInDocker chrome 91" bonigarcia/webdrivermanager:{project-version}
   ----
   
   WARNING: There is an https://bugs.chromium.org/p/chromedriver/issues/detail?id=3857[open issue] with Chrome 92+ and Docker at the time of this writing. For this reason, the previous Docker container command uses Chrome 91. For further information, see <<known-issues, known issues>>.
  
positive.code: }
  ----
  
  To configure the WebDriverManager Agent, we need to specify the path of the WebDriverManager https://github.com/bonigarcia/webdrivermanager/releases/download/webdrivermanager-5.0.0/webdrivermanager-5.0.0-fat.jar[fat-JAR] using the JVM flag `-javaagent:/path/to/webdrivermanager-5.0.0-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:
  
negative.code: 
  For example, this https://github.com/bonigarcia/webdrivermanager/blob/master/src/test/java/io/github/bonigarcia/wdm/test/create/ChromeRemoteTest.java[test] shows how to start a Selenium Grid in standalone mode, resolving the driver with WebDriverManager and registering a Chrome browser in the Selenium Server. In addition, if we start Selenium Grid from the shell, we can complement it with WebDriverManager CLI to resolve the required drivers, as follows:
  
  [source,shell,subs="attributes+"]
  ----
  boni@ubuntu:~$ java -jar webdrivermanager-{project-version}-fat.jar resolveDriverFor chrome
  [INFO] Using WebDriverManager to resolve chrome
  [DEBUG] Detecting chrome version using online commands.properties
  [DEBUG] Running command on the shell: [google-chrome, --version]
  