In daemon mode QF-Test listens to RMI connections and provides an interface for remote test execution. This is useful for simplifying test execution in a distributed load-testing scenario (chapter 31), but also for integration with existing test management or test execution tools (chapter 26).
!!! Warning !!!
Anybody with access to the QF-Test daemon can start any program on the machine running the daemon with the rights of the user account that the daemon is running under, so access should be granted only to trusted users.
If you are not running the daemon in a secure environment where every user is trusted or if you are creating your own library to connect to the QF-Test daemon, you definitely should read section 53.3 about how to secure daemon communication with SSL.
To work with a daemon, you must first launch it on any computer in your network (of
course, this host can also be
|Example 23.9: Launching a QF-Test daemon
Note Important compatibility note:
Starting with QF-Test version 3.5, SSL is used for daemon communication by default. To
interact with a QF-Test version older than 3.5 you must start the daemon with an empty
-keystore <keystore file> argument in the form:
|Example 23.10: Launching a QF-Test daemon without SSL
If you omit the argument
-daemonport, the daemon will listen on QF-Test's
standard port 3543. You may check whether the daemon is running by means of the
If you want to launch a daemon on a remote host, you may use for instance ssh or VNC. Your network administrator knows whether and how this works. To follow the examples below, a local daemon will be sufficient.
The easiest way to get in touch with a daemon is running QF-Test from the command line in the calldaemon mode. The following example checks if a daemon is listening at the specified host and port:
|Example 23.11: Pinging a QF-Test daemon
In contrast to the
netstat command from above
works between different computers (if you check the daemon on your local computer,
you can omit the argument
What you actually want from a daemon is executing your test case(s) and getting back a run log file. It sounds and indeed looks quite similar to what you have seen before when running a test in batch mode:
|Example 23.12: Running a test case with the QF-Test daemon
Note In contrast to the batch mode, a 'Test case' or a 'Test set' node is always
referenced here by its qualified name, for instance "My Test set.My Test case" (just
-test <ID> may be used in batch mode). To execute the
suiteA.qft, you can simply omit the test case or write
If the daemon is running on a remote host, you have to specify it explicitly via
-daemonhost (default is
-daemonhost localhost). Note that
-suitedir refers to the remote host (where the daemon is
-runlog defines a local file.
In case you cannot easily observe the test running on a remote host, you may find it
convenient to add the argument
-verbose to get status output in the
console (on Windows, use
qftestc to see the output).
A running daemon, no matter whether local or remote, can be terminated with the
|Example 23.13: Terminating a QF-Test daemon
A complete list of the calldaemon parameters can be found in the chapter Command line arguments and exit codes.
Using the QF-Test command line to control a daemon was quite easy. On the other hand, to get all capabilities of a daemon, you have to deal with the daemon API. In this section we will concentrate on some basic examples, the whole interface is described in chapter 53.
To get started with the daemon API, insert a 'Server script' node with the following code:
|Example 23.14: Daemon API in a 'Server script'
The script shows the basic mechanisms to control a daemon:
createContext). The creation
of that object requires a QF-Test run-time license.
runTest) and to
query about its current state.
waitForRunState waits during the
defined timeout (in milliseconds) until the specified state has occurred. In the
example above, we wait for the test to terminate within one minute.
getResult (cf. Exit codes for QF-Test).
Note To keep it small and simple, the example script does not contain any error handling. However, particularly when working with a daemon, you should check every method call.
Note Driving a daemon from a 'Server script' has the disadvantage of consuming an additional QF-Test license to run the script node interactively or in batch mode. However, this doesn't apply nor for the above-mentioned calldaemon mode neither for the case when controlling a daemon outside QF-Test (see below).
The usage of the daemon API is not restricted to 'Server scripts'. Outside
QF-Test a daemon can be contacted by means of a Java program or, more easily, a Groovy
script. The following Groovy script works with several running daemons and may serve
as a starting point for load tests. Suppose we have started some daemons in our
network, each on a separate machine. We want to execute a test case simultaneously
by all of the daemons and we want to save a run log for every single test run
daemon1.qrl, ..., daemonN.qrl). The test suite containing the test case
to be executed may be available for all daemon instances via the network drive
|Example 23.15: Groovy daemon script
To run that Groovy script, you need the QF-Test libraries
qflib.jar as well as the Groovy library,
which is also part of the QF-Test installation. The following batch script shows how it
|Example 23.16: Batch script
calldaemon.bat to run
When accessed from externally, the
DaemonLocator can only determine the default keystore
to encrypt the daemon communication automatically, if the
qftest.jar file is loaded from the
QF-Test-directory (as shown in the batch script). Alternatively (as seen in the groovy script),
the keystore can be specified explicetly by calling
or indirectly with the system properties
To make the daemon example a load test (cf. chapter 31), you have
to synchronize the test runs inside of "My test case" (e. g. after starting the SUT).
This can be done by means of the
|Example 23.17: Groovy 'Server script' node to synchronize the test runs
machines denotes the number of hosts with a daemon running
on them. Best define it in the 'Test suite' node of the test suite with a default value
1. When running the Groovy script, it will be overwritten with the
|Last update: 2/26/2024
Copyright © 1999-2024 Quality First Software GmbH