QF-Test Launcher (qftest.jar)

The QF-Test launcher allows interfacing with QF-Test (.qft) scripts.
It has been tested with QF-Test v3.4.11.


The qftest.xml file is just a template and must NOT be edited. It's used by the system to build dynamically the form that the user will be able to fill in from the GUI when creating a custom execution configuration.

Parameter Description
Test root path This must indicate where are located all the .qft scripts.
This is a root path. Each test in XStudio has a canonical path that will be appended to this path.
This path MUST not include an ending slash.

Default value is: Y:/Externals/qftest/scripts
QF-Test install path This must indicate where is installed QF-Test on the host.

Default value is: C:/Program Files/qfs/qftest/qftest-3.4.11
Options This must indicate the options passed to the interpreter. This shouldn't be modified.

Default value is: -batch -compact

These values can be changed while creating the campaign session from XStudio.

Note about file path parameters:

Any parameter referring to a file or folder path (for instance Test root path) can be provided either using \ separator (if the tests are going to be executed on a Windows agent) or / separator (if the tests are going to be executed on a linux or MacOSX agent).

On windows, if you provide a path containing a, OS-localizable folder such as C:\Program Files, always prefer the English version (i.e. NOT C:\Programmes if you're using a french-localized Windows) or the corresponding native environment variable (i.e. %PROGRAMFILES%).


  • Each test in XStudio must have his dedicated .qft script. The name of the script MUST be equal to the name of the test.

  • The interpreter is executed by the launcher using this syntax:

    "<qftestInstallPath>/bin/qftestc.exe" <Options>
    -runlog "<testRootPath>/<testPath>/<testName>_<testcaseName>/log_<testName>_<testcaseName>"
    -report "<testRootPath>/<testPath>/<testName>_<testcaseName>/report_<testName>_<testcaseName>"
    -test "<testcaseName>" "<testRootPath>/<testPath>/<testName>.qft"

Tutorial: Creating and executing QF-Test tests

In this tutorial, we will learn to run some QF-Test test scripts.


Install QF-Test in the folder C:\\Program Files (x86)

Some demo projects and tests are by default included with QF-Test in the folder C:\\Program Files (x86)\\qfs\\qftest\\qftest-3.4.11\\demo. We are going to use the project C:\\Program Files (x86)\\qfs\\qftest\\qftest-3.4.11\\demo\\carconfig_en

Create a dedicated category for QF-Test and create a test

  • create a category QF-Test in the test tree associated to the launcher qftest.jar
  • under this category, create (somewhere in the tree) a test with name carconfig_en and with a canonical path set to carconfig.

Create 2 test cases under this test

  • under this test, create a test case with name Override Element Demo.
  • under this test, create a test case with name Custom check.

Creating a test campaign

  • create a campaign including only the test carconfig_en
  • create a campaign session specifying in the configuration:
    • Test root path: C:/Program Files (x86)/qfs/qftest/qftest-3.4.11/demo
    • QF-Test install path: C:/Program Files (x86)/qfs/qftest/qftest-3.4.11
    • Options: -batch -compact

Run a campaign session

Run the campaign session


WARNING: if you're running your tests on Windows, it may be required to run the tests as administrator.
Having an account with Administrators permissions may even not be enough in some cases (especially if you're using Windows 10) and you may need to disable completely the UAC (User Access Control) on your computer.

To do so:
  • Press the Windows + R key combination
  • Type in regedit
  • Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
  • In the right-side pane, look for EnableLUA and set the value 0
  • Close the registry editor
  • Restart your computer


If your tests are not executed correctly or are reporting only failures, this is very likely because your configuration is incorrect or because you used a wrong naming convention for your tests and test cases.

The best way to quickly find out what's wrong is to look at the traces generated by XStudio (or XAgent).
The traces always include the detailed description of what the launcher performs (command line execution, script execution, API calling etc.) to run a test case. So, if you experiment some problems, the first thing to do is to activate the traces and look at what's happening when you run your tests.

Then, try to execute manually in a cmd box the exact same commands.
This will normally fail the same way.
At this point, you needs to figure out what has to be changed in these commands in order to have them run properly.

When you have something working, compare these commands to what's described in the Process chapter above. This will tell you exactly what you need to change.

Most of the time, this is related to:
  • some incorrect values in some parameters of your configuration,
  • the name of your tests,
  • the name of your test cases,
  • the canonical path of your tests