scala-native
TestFramework remoteArgs not passed as args of Slave runner
It seems like whatever returned in 'master' runner's remoteArgs is not being passed as args to the 'slave' runner, is that expected behavior?
Hey, thank you for bringing this issue. Most of the testing framework was initially ported from Scala.js long time ago, which has based it implementation on https://github.com/sbt/junit-interface
As far as I know, the remote args are typically passed around and should not be lost at any point.
In case of JUnit - the only framework we are in control of, the remoteArgs are actually never used, so that's why they might not be passed when creating framework options.
Do you maybe have some examples where there might be issue with lack of remoteArgs? As pointed before I think we always pass them around.
