On Wed, June 13, 2012 12:17 pm, Shane Isbell wrote:
> Hi all,
>
> I'm working on an android provider for surefire. Generally, I have things
> working but have encountered a specific problem. The unit tests are
> running
> remotely on a device (not the build machine). For the surefire xml report,
>
I would somehow assume that the sensible way to implement an android
provider would be to extend the current forking logic to serialize the
entire fork to a remote machine. Furthermore there is already support
for bringing the system properties from the fork back to the plugin,
which would come for
Hi all,
I'm working on an android provider for surefire. Generally, I have things
working but have encountered a specific problem. The unit tests are running
remotely on a device (not the build machine). For the surefire xml report,
I need to pull in the system properties on the device, not those
