anchor.diff:  ----
   include::../../test/java/io/github/bonigarcia/seljup/test/generic/GenericTest.java[tags=snippet-in-doc,indent=0]
   ----
  +
  +=== Chrome DevTools
  +As of version 4.1.0, Selenium-Jupiter allows to inject `DevTools` instances in tests. This object used to send commands using the Chrome DevTools Protocol (CDP) to the driver declared just before in the test. For instance, the parameter `devTools` in following test allows to handle CDP commands of the browser handled with `driver`:
  +
  +[source,java]
  +----
  +include::../../test/java/io/github/bonigarcia/seljup/test/devtools/FullPageScreenshotTest.java[tags=snippet-in-doc,indent=0]
  +----
  +
   
   === Single session
   By default, the instances provided by _Selenium-Jupiter_ (e.g. `ChromeDriver`, `FirefoxDriver`, etc.) are created _before each_ test, and are disposed _after each_ test. This default behavior can be changed using the class-level annotation `@SingleSession`. The instances provided in this case will be created _before all_ tests and are disposed _after all_ tests.
  
positive.code: include::../../test/java/io/github/bonigarcia/seljup/test/local/SafariTest.java[tags=snippet-in-doc,indent=0]
  ----
  
  === Remote browsers
  Selenium-Jupiter also allows controlling remote browsers. These browsers are typically provided by a https://www.selenium.dev/documentation/en/grid/[Selenium Grid] infrastructure or a cloud provider (such as https://saucelabs.com/[Sauce Labs], https://www.lambdatest.com/[LambdaTest], etc.). To this aim, Selenium-Jupiter provides two annotations:
  
  
negative.code: ----
  
  You can find an example of an equivalent remote test but defining the remote URL and capabilities at field-level https://github.com/bonigarcia/selenium-jupiter/blob/master/src/test/java/io/github/bonigarcia/seljup/test/remote/RemoteChromeTest.java[here]. A similar example, but using Sauce Labs is this https://github.com/bonigarcia/selenium-jupiter/blob/master/src/test/java/io/github/bonigarcia/seljup/test/remote/SauceLabsTest.java[one].
  
  As of version 4.1.0, Selenium-Jupiter supports remote browsers in https://appium.io/[Appium] 2. To use this feature, you need to specify the type `AppiumDriver`, and also the Appium server URL and capabilities. The following test shows a basic example:
  
  
  [source,java]
  ----
  include::../../test/java/io/github/bonigarcia/seljup/test/remote/AppiumTest.java[tags=snippet-in-doc,indent=0]
  ----
  
  === Docker browsers
  Selenium-Jupiter allows using browsers in Docker containers in an effortless manner. To that aim, we need to associate the `@DockerBrowser` annotation to parameters of the type `WebDriver` or `RemoteWebDriver` in Jupiter tests. Simply with that, Selenium-Jupiter discovers the latest version of the browser in Docker Hub, pulls this image (if necessary), and starts the browser in the Docker container. The following example shows how to use this feature with a Chrome browser in Docker:
  