Custom Launchers

Custom Launchers

Let�s take a basic example: you have two different types of tests:
  • native executables (you currently just have to run the executables, logs are printed out on the console, exit code gives the result of the test),
  • java class files (these are java class file with a main entry point; all classes inherit from the TestClass class. You usually run them by calling the java interpreter on each test using .bat or .sh scripts).

With a very minimum effort, you can make all these tests (maybe several thousands of tests) manageable by XStudio. To do this, you just have to develop 2 launchers (10 lines of code each).
Custom Launchers

Figure 12 � Custom Launchers
These launchers will have the responsibility to:
  • translate the abstract execution orders from XStudio to real operations (instantiate the test and execute it),
  • return results to XStudio.

Of course, the launcher interface/API is wider than just a run() method but the run() method is the principal one.
I�m currently working on the Developer�s Guide that will explain in detail how to develop you own launcher.