It would be good to have in an ability to automatically start/stop services (external processes) from the JavaTest harness for some JCK test run configurations. Also it would be good to have port number management capabilities as well as support for concurrent test execution.

Currently the JCK requires the following services to be started:
   - the passive JavaTest agent running on reference JVM for distributed tests using distributed framework. [1], [2]
   - "jdk/bin/rmid" for Java RMI tests [3]
   - "jdk/bin/tnameserv" for Corba test [4]

-------
[1] http://j2se.sfbay.sun.com/web/bin/view/TCKs/DistributedTest
[2] http://javaweb.sfbay/java/re/jck/6b/promoted/fcs/latest/binaries/JCK-runtime-6b/doc/jck/html/p8.html#gdcvq
[3] http://javaweb.sfbay/java/re/jck/6b/promoted/fcs/latest/binaries/JCK-runtime-6b/doc/jck/html/p8.html#gdkrq
[4] http://javaweb.sfbay/java/re/jck/6b/promoted/fcs/latest/binaries/JCK-runtime-6b/doc/jck/html/p8.html#gdcnl