Fake HTTP headers implementation.
Fake HTTP headers implementation.
Headers data.
A Request
with a few extra methods that are useful for testing.
A Request
with a few extra methods that are useful for testing.
the body content type.
Helper methods for building FakeRequest values.
A structural type indicating there is an application.
A trait declared on a class that contains an def app: Application
, and can provide
instances of a class.
A trait declared on a class that contains an def app: Application
, and can provide
instances of a class. Useful in integration tests.
Helper functions to run tests.
Play specs2 specification.
Play specs2 specification.
This trait excludes some of the mixins provided in the default specs2 specification that clash with Play helpers methods. It also mixes in the Play test helpers and types for convenience.
Provided as an implicit by WithServer and WithBrowser.
A test browser (Using Selenium WebDriver) with the FluentLenium API (https://github.com/Fluentlenium/FluentLenium).
A test browser (Using Selenium WebDriver) with the FluentLenium API (https://github.com/Fluentlenium/FluentLenium).
The WebDriver instance to use.
A test web server.
A test web server.
The server configuration.
The Application to load in this server.
The type of server to use. If not provided, uses Play's default provider.
Used to run specs within the context of a running application.
Used to run specs within the context of a running application loaded by the given ApplicationLoader
.
Used to run specs within the context of a running server, and using a web browser
Used to run specs within the context of a running server.
A standalone test client that is useful for running standalone integration tests.
Exposes methods to make using requests with CSRF tokens easier.
Object with helper methods for building FakeRequest values.
Object with helper methods for building FakeRequest values. This object uses a play.api.mvc.request.DefaultRequestFactory with default configuration to build the requests.
In 99% of cases, when running tests against the result body, you don't actually need a materializer since it's a strict body.
In 99% of cases, when running tests against the result body, you don't actually need a materializer since it's a strict body. So, rather than always requiring an implicit materializer, we use one if provided, otherwise we have a default one that simply throws an exception if used.
A temporary file creator with no implementation.
Helper utilities to build TestBrowsers
Contains test helpers.