You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am integrating Lagom integration tests with Optic which requires that the Lagom service start on a specific port (which Optic provides). Therefore I need to be able to specify the port on which a Lagom application will start up when TestServer.startServer is invoked.
Actual Behavior
The port is hard-coded in ServerConfig to Some(0), which means the service will always start on a dynamically assigned port.
I propose that instead we allow the user to specify a port as part of the Setup configuration. Ideally, the user should have control of all ports (http, https, and any dependent services which are started, such as Cassandra/JDBC).
Lagom Version
Current (1.6.4)
API (Scala / Java / Neither / Both)
Scala (
TestKit
)Expected Behavior
I am integrating Lagom integration tests with Optic which requires that the Lagom service start on a specific port (which Optic provides). Therefore I need to be able to specify the port on which a Lagom application will start up when
TestServer.startServer
is invoked.Actual Behavior
The port is hard-coded in
ServerConfig
toSome(0)
, which means the service will always start on a dynamically assigned port.https://github.com/lagom/lagom/blob/master/testkit/scaladsl/src/main/scala/com/lightbend/lagom/scaladsl/testkit/ServiceTest.scala#L330
I propose that instead we allow the user to specify a port as part of the
Setup
configuration. Ideally, the user should have control of all ports (http, https, and any dependent services which are started, such as Cassandra/JDBC).See also #1584
The text was updated successfully, but these errors were encountered: