From 25bc6acafd453cbed9604973e0a6f7d7e73da543 Mon Sep 17 00:00:00 2001 From: Matthias Kurz Date: Fri, 25 Aug 2023 20:13:15 +0200 Subject: [PATCH] A random port is used now --- .../main/tests/ScalaFunctionalTestingWithScalaTest.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/working/scalaGuide/main/tests/ScalaFunctionalTestingWithScalaTest.md b/docs/manual/working/scalaGuide/main/tests/ScalaFunctionalTestingWithScalaTest.md index 939f5b6f..3357964f 100644 --- a/docs/manual/working/scalaGuide/main/tests/ScalaFunctionalTestingWithScalaTest.md +++ b/docs/manual/working/scalaGuide/main/tests/ScalaFunctionalTestingWithScalaTest.md @@ -39,7 +39,7 @@ If all tests in your test class require separate server instances, use [`OneServ @[scalafunctionaltest-oneserverpertest](code/oneserverpertest/ExampleSpec.scala) -The `OneServerPerSuite` and `OneServerPerTest` traits provide the port number on which the server is running as the `port` field. By default this is 19001, however you can change this either overriding `port` or by setting the system property `testserver.port`. This can be useful for integrating with continuous integration servers, so that ports can be dynamically reserved for each build. +The `OneServerPerSuite` and `OneServerPerTest` traits provide the port number on which the server is running as the `port` field. By default this is a random port, however you can change this either overriding `port` or by setting the system property `testserver.port`. This can be useful for integrating with continuous integration servers, so that ports can be dynamically reserved for each build. You can also customize the `Application` by overriding `app`, as demonstrated in the previous examples.