I don't think the `Scope` is really playing a role...
# tornadofx
c
I don't think the
Scope
is really playing a role here. The
app.scope
instance remains the same between tests since nothing in the test depends on a unique
Scope
in this case. Looking through the TornadoFX source, I see in
Async.kt
both of the thread pools are assigned as
val
in global scope. So, if TestFX is closing down and trying to start back up the app between cycles, those thread pools would linger to the next test cycle in a shut down state.