4 Replies Latest reply on Apr 4, 2005 10:33 PM by Clebert Suconic

    distributed test framework

    Tom Elrod Master

      The distributed test framework under the remoting module tests can be used to start multiple client and server instances, along with a driver instance that will use a remote barrier for starting and stopping all the instances. This allows users to create a server and multiple client instances who will execute their client test code at the same time. The driver collects the junit assert results from the clients (and/or server).

      This was created for remoting code testing because I need the following:

      1. Ability to create one more clients that execute against a server at the same time.
      2. A way to consolidate test failure reporting from clients and server.
      3. Simulation of seperate processes between client and server for testing of remote classloading.
      4. A single class that can be executed as a JUnit TestCase so that can be included within general testsuite run and failures reported within general testsuite results.

      Am certainly not tied to dtf, but would need something that meets these requirements if go with something else.

      The biggest problem with dtf currently is timing issues. Since the driver actually creates new instances for the clients and server to run in, and ultimately have not direct control of these after started, have to setup timeouts for the cases in which can not detect proper start up or shutdown of these new processes. These timeouts vary widely depending on initialization on startup and even on the hardware the tests run on (since can start up much slower on slower hardware).