Instead of 'ensuring to start' a seaside server for executing tests, I needed to be able to stop the server as well after running a testsuite. Converting the Seasideserver that is started for the tests to a testresource makes that possible.
This is required to fix broken tests in Gemstone after adding Parasol to execute the functional tests. The gemservers have separate testcases and having started gem servers from other testcases interferes with a correct run. Context: https://github.com/SeasideSt/Seaside/pull/1199
There is a breaking change: 'shouldEnsureSeasideServerStarted' is now on the class side instead of the instance side. It still controls if a Seaside server will be started.
Instead of 'ensuring to start' a seaside server for executing tests, I needed to be able to stop the server as well after running a testsuite. Converting the Seasideserver that is started for the tests to a testresource makes that possible.
This is required to fix broken tests in Gemstone after adding Parasol to execute the functional tests. The gemservers have separate testcases and having started gem servers from other testcases interferes with a correct run. Context: https://github.com/SeasideSt/Seaside/pull/1199