I suspect the "beasting" script would be best simulated by creating X test tasks (with different names but identical configuration). Then gradle can take care of parallelism serving those tasks to its worker VMs. This would accomplish many things at once: everything would run from within a single gradle parent process (daemon or not), tests would be run in parallel, the first failure could abort execution of subsequent tasks, etc.
There are some open questions - whether beasting should run with the same temporary folders (probably not) whether gradle will be smart enough to collect report for multiple test with the same name (probably not)... you know - the devil is in the details. But I think it'd be an ideal way to do it: no need for external trickery, scripts, multi-platform compatibility, etc. Anyone up to the challenge? :) Dawid --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
