com.lightbend.lagom.scaladsl.testkit
ServiceTest
Related Doc:
package testkit
When the server is started you can get the service client and other Guice bindings here.
The default Setup configuration, which has persistence enabled.
Start the test server with the given setup.
Start the test server with the given setup. You must stop the server with
the stop method of the returned TestServer when the test is finished.
When your test have several test methods, and especially when using persistence, it is
faster to only start the server once in a static method annotated with @BeforeClass
and stop it in a method annotated with @AfterClass. Otherwise withServer() is
more convenient.
You can get the service client from the returned TestServer.
Start the test server with the given setup and run the block (lambda).
Start the test server with the given setup and run the block (lambda). When
the block returns or throws the test server will automatically be stopped.
This method should be used when the server can be started and stopped for each test method. When your test have several test methods, and especially when using persistence, it is faster to only start the server once with #startServer.
You can get the service client from the TestServer that is passed as parameter
to the block.
Support for writing functional tests for one service. The service is running in a server and in the test you can interact with it using its service client, i.e. calls to the service API.
The server is ran standalone without persistence, pubsub or cluster features enabled. Cassandra is also disabled by default. If your service require either of these features you can enable them in the
Setup.There are two different styles that can be used. It is most convenient to use ServiceTest.withServer(), since it automatically starts and stops the server before and after the given block. When your test have several test methods, and especially when using persistence, it is faster to only ServiceTest.startServer() the server once in a before all tests hook, and then stop it in an after all test hook.