Creates a new instance of a valid Selenium WebDriver, or if a driver is unavailable on the host platform,
returns a BrowserFactory.UnavailableDriver that includes
the exception that indicated the driver was not supported on the host platform and an appropriate
error message.
Creates a new instance of a valid Selenium WebDriver, or if a driver is unavailable on the host platform,
returns a BrowserFactory.UnavailableDriver that includes
the exception that indicated the driver was not supported on the host platform and an appropriate
error message.
an new instance of a Selenium WebDriver, or a BrowserFactory.UnavailableDriver
if the desired WebDriver is not available on the host platform.
Places the WebDriver provided by webDriver into the ConfigMap under the key
org.scalatestplus.play.webDriver to make
it available to nested suites; calls super.run; and lastly ensures the WebDriver is stopped after
all tests and nested suites have completed.
Places the WebDriver provided by webDriver into the ConfigMap under the key
org.scalatestplus.play.webDriver to make
it available to nested suites; calls super.run; and lastly ensures the WebDriver is stopped after
all tests and nested suites have completed.
an optional name of one test to run. If None, all relevant tests should be run.
I.e., None acts like a wildcard that means run all relevant tests in this Suite.
the Args for this run
a Status object that indicates when all tests and nested suites started by this method have completed, and whether or not a failure occurred.
An implicit instance of WebDriver, created by calling createWebDriver.
An implicit instance of WebDriver, created by calling createWebDriver.
If there is an error when creating the WebDriver, UnavailableDriver will be assigned
instead.
Automatically cancels tests with an appropriate error message when the webDriver field is a UnavailableDriver,
else calls super.withFixture(test)
Automatically cancels tests with an appropriate error message when the webDriver field is a UnavailableDriver,
else calls super.withFixture(test)
Trait that provides a new Selenium
WebBrowserinstance per ScalaTestSuite.This
SuiteMixintrait's overriddenrunmethod places a reference to theWebDriverprovided bywebDriverunder the keyorg.scalatestplus.play.webDriver. This allows any nestedSuites to access theSuite'sWebDriveras well, most easily by having the nestedSuites mix in the ConfiguredBrowser trait. On the status returned bysuper.run, this trait's overriddenrunmethod registers a block of code to close theWebDriverto be executed when theStatuscompletes, and returns the sameStatus. This ensures theWebDriverwill continue to be available until all nested suites have completed, after which theWebDriverwill be closed. This trait also overridesSuite.withFixtureto cancel tests automatically if the relatedWebDriveris not available on the host platform.This trait's self-type, ServerProvider, will ensure a
TestServerandFakeApplicationare available to each test. The self-type will require that you mix in either OneServerPerSuite, OneServerPerTest, ConfiguredServer before you mix in this trait. Your choice among these threeServerProviders will determine the extent to which one or moreTestServers are shared by multiple tests.Here's an example that shows demonstrates of the services provided by this trait. Note that to use this trait, you must mix in one of the driver factories (this example mixes in FirefoxFactory):
If you have many tests that can share the same `FakeApplication`, `TestServer`, and `WebDriver`, and you don't want to put them all into one test class, you can place them into different "nested" `Suite` classes. Create a master suite that extends `OneServerPerSuite` and declares the nested `Suite`s. Annotate the nested suites with `@DoNotDiscover` and have them extend `ConfiguredBrowser`. Here's an example: It is possible to use `OneBrowserPerSuite` to run the same tests in more than one browser. Nevertheless, you should consider the approach taken by [[org.scalatestplus.play.AllBrowsersPerSuite AllBrowsersPerSuite]] and [[org.scalatestplus.play.AllBrowsersPerTest AllBrowsersPerTest]] instead, as it requires a bit less boilerplate code than `OneBrowserPerSuite` to test in multiple browsers. If you prefer to use `OneBrowserPerSuite`, however, simply place your tests in an abstract superclass, then define concrete subclasses for each browser you wish to test against. Here's an example: The concrete subclasses include tag annotations describing the browser used to make it easier to include or exclude browsers in specific runs. This is not strictly necessary since if a browser is not supported on the host platform the tests will be automatically canceled. For example, here's how the output would look if you ran the above tests on a platform that did not support Selenium drivers for Chrome or Internet Explorer using sbt: For comparison, here is what the output would look like if you just selected tests tagged with `FirefoxBrowser` in sbt: