One was for the original integration tests, the other was stood up with coroutines (via runTest and Turbine) to do pull based testing of multiple Workflows.
We should pick a path and support it.
Right now launchForTestingFromStart/StateWith... does not support specifying RuntimeConfig as a parameter - it must be done via a System Property and JvmRuntimeConfigTools (usually shuttled there via a gradle property - handy, but not clear).
One was for the original integration tests, the other was stood up with coroutines (via
runTest
andTurbine
) to do pull based testing of multiple Workflows.We should pick a path and support it.
Right now launchForTestingFromStart/StateWith... does not support specifying
RuntimeConfig
as a parameter - it must be done via a System Property and JvmRuntimeConfigTools (usually shuttled there via a gradle property - handy, but not clear).