Launchers
The problem
Test management software often require from the customers to contract some services to third-party companies (or the editor itself) to "connect" their tests with the test management system. This emphasizes severals problems:- this has an extremely high cost
- the customer has not his independance guaranted
- adapting the system to a new type of test may be costly in terms of time
- and more...
The fix
XStudio provides a complete and extremely simple SDK API that allows you to develop your connector yourself. This connector is called a "launcher" in the XQual terminology. This is what makes the "link" between the generic test management software (XStudio) and your very specific tests.
When you finish the development of your launcher, you just need to associate the resulting jar with a category in the test tree. As simple as that !
Note that you can also associate to your jar an XML that describes the configurable parameters for this launcher. At execution or schedule time XStudio will interpret it as a form to let you enter some configuration parameters. Those parameters will be used by your launcher at run time.
For instance:
<form name="Timing">
<formItem type="slider"
id="0"
name="max time between testcases (ms)"
value="0"
value="2000"
min="0"
max="10000"
readOnly="false"/>
<formItem type="boolean"
id="1"
name="prerun and postrun take time to execute"
value="true"
readOnly="false"/>
<formItem type="integer"
id="2"
name="time to execute prerun (ms)"
value="500"
readOnly="false"/>
<formItem type="integer"
id="3"
name="time to execute postrun (ms)"
value="500"
readOnly="false"/>
</form>
...will be interpreted as:
This mechanism is extremey powerful because it allows you to automate the execution of your tests very rapidely. In most of the cases, only a few tenth of lines of java are sufficient.
Learn more about the integrated "Interaction" module.
Learn more about the integrated "Action" module.
