anchor.diff:  as the ”browser specification“. For a full list of available browsers, versions and operating systems refer to your cloud provider's documentation:
   
   * link:https://saucelabs.com/platforms[SauceLabs platform list]
  +* link:https://www.lambdatest.com/list-of-browsers[LambdaTest platform and browser list]
   * link:http://www.browserstack.com/list-of-browsers-and-platforms?product=automate[BrowserStack Browsers and Platforms list]
   
  -Please note that Geb Gradle plugins can set the `geb.saucelabs.browser`/`geb.browserstack.browser` system properties for you using the aforementioned format.
  +Please note that Geb Gradle plugins can set the `geb.saucelabs.browser`/`geb.lambdatest.browser`/`geb.browserstack.browser` system properties for you using the aforementioned format.
   
   Following the browser specification are the username and access key used to identify your account with the cloud provider.
   The example uses two environment variables to access this information.
  
positive.code: 
  When you want to perform web testing on multiple browsers and operating systems, it can be quite complicated to maintain machines for each of the target environments.
  There are a few companies that provide "remote web browsers as a service", making it easy to do this sort of matrix testing without having to maintain the multiple browser installations yourself.
  Geb provides easy integration with two such services, link:https://saucelabs.com/[SauceLabs] and link:http://www.browserstack.com/[BrowserStack].
  This integration includes two parts: assistance with creating a driver in `GebConfig.groovy` and a Gradle plugin.
  
  == Creating a driver
  
  For both SauceLabs and BrowserStack, a special driver factory is provided that, given a browser specification as well as an username and access key, creates an instance of `RemoteWebDriver` configured
  to use a browser in the cloud.
  Examples of typical usage in `GebConfig.groovy` are included below.
  They will configure Geb to run in SauceLabs/BrowserStack if the appropriate system property is set, and if not it will use whatever driver that is configured.
  This is useful if you want to run the code in a local browser for development.
  In theory you could use any system property to pass the browser specification but `geb.saucelabs.browser`/`geb.browserstack.browser` are also used by the Geb Gradle plugins, so it's a good idea to
  stick with those property names.
  
  The first parameter passed to the `create()` method is a ”browser specification“ and it should be a list of required browser capabilities in Java properties file format:
  
negative.code: }
  ----
  
  
  [[lambda-test-driver-factory]]
  === `LambdaTestDriverFactory`
  
  The following is an example of utilizing `LambdaTestDriverFactory` in `GebConfig.groovy` to configure a driver that will use a browser provided in the LambdaTest cloud.
  
  [source,groovy]
  ----
  def lambdaTestBrowser = System.getProperty("geb.lambdatest.browser")
  if (lambdaTestBrowser) {
      driver = {
         def username = System.getenv("GEB_LAMBDATEST_USERNAME")
         assert username
         def accessKey = System.getenv("GEB_LAMBDATEST_AUTHKEY")
         assert accessKey
         new LambdaTestDriverFactory().create(lambdaTestBrowser, username, accessKey)
      }
  }
  ----
  
  If using `TunnelIdentifier` support:
  
  [source,groovy]
  ----
  def lambdaTestBrowser = System.getProperty("geb.lambdatest.browser")
  if (lambdaTestBrowser) {
      driver = {
         def username = System.getenv("GEB_LAMBDATEST_USERNAME")
         assert username
         def accessKey = System.getenv("GEB_LAMBDATEST_AUTHKEY")
         assert accessKey
         def tunnelId = System.getenv("GEB_LAMBDATEST_TUNNELID")
         assert localId
         new LambdaTestDriverFactory().create(lambdaTestBrowser, username, accessKey, tunnelId)
      }
  }
  ----
  
  == Gradle plugins
  
  For SauceLabs, LambdaTest and BrowserStack, Geb provides a Gradle plugin which simplifies declaring the account and browsers that are desired, as well as configuring a tunnel to allow the cloud provider to
  access local applications.
  These plugins allow easily creating multiple `Test` tasks that will have the appropriate `geb.PROVIDER.browser` property set (where _PROVIDER_ is either `saucelabs`, `lambdatest` or `browserstack`).
  The value of that property can be then passed in configuration file to <<sauce-labs-driver-factory>>/<<lambda-test-driver-factory>>/<<browser-stack-driver-factory>> as the ”browser specification“.
  Examples of typical usage are included below.
  
  === geb-saucelabs plugin
  