 |  |  |  |  |  |  |  |
| Version 8.0.1 |
The call syntax for interactive and batch mode varies widely since some
command line arguments are specific to interactive mode or batch mode or even sub-modes
of batch mode.
Note that all of the arguments have sensible default values which you only
need to override for special cases. In most cases you'll only need to
execute either qftest [<suite> | <run log>]*
to run QF-Test in interactive mode, or qftest to execute a test in batch mode.
-batch
[-runlog [<file>]] [-report <directory>] <suite>
5.2+
For maximum flexibility the names of all QF-Test arguments are case-insensitive and embedded '-', '_', '.' and
':' characters are ignored, so -report.html is equivalent to --reportHtml or
-report-html. The latter is the officially documented form because it avoids conflicts with
Windows PowerShell.
WindowsThe program qftest.exe is a Windows GUI application.
When started from a command shell, it will not wait for QF-Test to terminate but return
immediately. Thus, when executing a test in batch mode, you cannot see whether QF-Test has
finished or not (you may put the command into a .bat file to deal with this behaviour).
Furthermore you won't see any output from QF-Test in the console window when using
qftest.exe.
For both reasons you may prefer to utilize the qftestc.exe Console application
when launching QF-Test from a command shell: It waits for QF-Test to terminate and print output
from 'Server scripts' will be displayed in the console window.
Apart from that, everything said about qftest.exe in this chapter holds true
for qftestc.exe too.
Mac In case the macOS App is used those parameters can be defined directly in QF-Test via »Edit«-»Options« under General->Startup (please also see the macOS specific note under Starting QF-Test).
qftest [-dbg]
[-java <executable>(deprecated)] [-noconsole]
[-J<java-argument>]*
[-allow-shutdown [<shutdown ID>]]
[-daemon]
[-daemonhost <host>]
[-daemonport <port>]
[-daemonrmiport <port>]
[-dontkillprocesses]
[-engine <engine>]
[-groovydir <directory>]
[-help]
[-ipv6]
[-javascriptdir <directory>]
[-jythondir <directory>]
[-jythonport <number>]
[-keybindings <value>]
[-keystore <keystore file>]
[-keypass <keystore password>]
[-libpath <path>]
[-license <file>]
[-license-waitfor <seconds>]
[-logdir <directory>]
[-noplugins]
[-noupdatecheck]
[-option <name>=<value>]
[-options <file>]
[-plugindir <directory>]
[-port <number>]
[-reuse]
[-run]
[-runlogdir <directory>]
[-runtime]
[-serverhost <host>]
[-shell <executable>]
[-shellarg <argument>]
[-suitesfile <file>]
[-systemcfg <file>]
[-systemdir <directory>]
[-tempdir <directory>]
[-test <n>|<ID>]*
[-usercfg <file>]
[-userdir <directory>]
[-variable <name>=<value>]*
[-version]
[<suite> | <run log>]*
There are several sub-modes for running QF-Test in batch mode. The default is to execute one or more test suites. Alternatively QF-Test can be invoked to create test documentation from test suites or reports from run logs. QF-Test can also be run in daemon mode where it sits in the background waiting for calls from the outside telling it what to do (see chapter 54 for further information about the daemon mode). Finally, showing help or version information can also be seen as separate sub-modes.
To execute one or more test suites and create a run log and/or report as a result, use:
qftest -batch [-run]
[-dbg] [-java <executable>(deprecated)] [-noconsole]
[-J<java-argument>]*
[-allow-shutdown [<shutdown ID>]]
[-clearglobals]
[-compact]
[-engine <engine>]
[-exitcode-ignore-exception]
[-exitcode-ignore-error]
[-exitcode-ignore-warning]
[-groovydir <directory>]
[-ipv6]
[-javascriptdir <directory>]
[-jythondir <directory>]
[-jythonport <number>]
[-keystore <keystore file>]
[-keypass <keystore password>]
[-libpath <path>]
[-license <file>]
[-license-waitfor <seconds>]
[-logdir <directory>]
[-nolog]
[-nomessagewindow]
[-noplugins]
[-option <name>=<value>]
[-options <file>]
[-plugindir <directory>]
[-port <number>]
[-report <directory>]
[-report-checks]
[-report-customdir <directory>]
[-report-doctags]
[-report-errors]
[-report-exceptions]
[-report-html <directory>]
[-report-ignorenotimplemented]
[-report-ignoreskipped]
[-report-junit <directory>]
[-report-name <name>]
[-report-nodeicons]
[-report-passhtml]
[-report-piechart]
[-report-include-suitename]
[-report-scale-thumbnails <percent>]
[-report-teststeps]
[-report-thumbnails]
[-report-warnings]
[-report-xml <directory>]
[-runid <ID>]
[-runlogdir <directory>]
[-runlog [<file>]]
[-runtime]
[-serverhost <host>]
[-shell <executable>]
[-shellarg <argument>]
[-sourcedir <directory>]
[-suitesfile <file>]
[-splitlog]
[-systemcfg <file>]
[-systemdir <directory>]
[-test <n>|<ID>]*
[-threads <number>]
[-userdir <directory>]
[-variable <name>=<value>]*
[-verbose [<level>]]
<suite>+
The following parameters can be specified when executing a test case by calling a daemon:
qftest -batch -calldaemon
[-cleanup] [-clearglobals]
[-dbg] [-java <executable>(deprecated)] [-noconsole] [-J<java-argument>]*
[-daemonhost <host>]
[-daemonport <port>]
[-exitcode-ignore-exception]
[-exitcode-ignore-error]
[-exitcode-ignore-warning]
[-ipv6]
[-keystore <keystore file>]
[-keypass <keystore password>]
[-nomessagewindow]
[-ping]
[-option <name>=<value>]
[-options <file>]
[-runid <ID>]
[-runlogdir <directory>]
[-runlog [<file>]]
[-startclean]
[-startsut]
[-stopclean]
[-stoprun]
[-systemdir <directory>]
[-suitedir <dir>]
[-systemdir <directory>]
[-terminate]
[-timeout <milliseconds>]
[-userdir <directory>]
[-variable <name>=<value>]*
[-verbose [<level>]]
<suite#test case>
qftest -batch -convertxml [-convertxml-indent <number>] [-convertxml-linelength <number>] [-convertxml-utf8 <true|false>] (<suite> | <directory>)+
Package or test case documentation can be create for one or more test suites or whole directories. This is described further in chapter 23. The command line syntax is:
qftest -batch -gendoc
[-dbg] [-java <executable>(deprecated)] [-noconsole]
[-J<java-argument>]*
[-license <file>]
[-license-waitfor <seconds>]
[-nomessagewindow]
[-option <name>=<value>]
[-options <file>]
[-pkgdoc <directory>]
[-pkgdoc-dependencies]
[-pkgdoc-doctags]
[-pkgdoc-html <directory>]
[-pkgdoc-includelocal]
[-pkgdoc-nodeicons]
[-pkgdoc-passhtml]
[-pkgdoc-sortpackages]
[-pkgdoc-sortprocedures]
[-pkgdoc-xml <directory>]
[-sourcedir <directory>]
[-systemdir <directory>]
[-testdoc <directory>]
[-testdoc-doctags]
[-testdoc-followcalls]
[-testdoc-html <directory>]
[-testdoc-nodeicons]
[-testdoc-passhtml]
[-testdoc-sorttestcases]
[-testdoc-sorttestsets]
[-testdoc-teststeps]
[-testdoc-xml <directory>]
(<suite> | <directory>)+
To create a report from one or more run logs or whole directories use:
qftest -batch -genreport
[-dbg] [-java <executable>(deprecated)] [-noconsole]
[-J<java-argument>]*
[-license <file>]
[-license-waitfor <seconds>]
[-nomessagewindow]
[-option <name>=<value>]
[-options <file>]
[-report <directory>]
[-report-checks]
[-report-customdir <directory>]
[-report-doctags]
[-report-errors]
[-report-exceptions]
[-report-html <directory>]
[-report-ignorenotimplemented]
[-report-ignoreskipped]
[-report-junit <directory>]
[-report-name <name>]
[-report-nodeicons]
[-report-passhtml]
[-report-piechart]
[-report-include-suitename]
[-report-scale-thumbnails <percent>]
[-report-teststeps]
[-report-thumbnails]
[-report-warnings]
[-report-xml <directory>]
[-runlogdir <directory>]
(<run log> | <directory>)+
To run QF-Test in daemon mode as described chapter 54 use:
qftest -batch -daemon
[-dbg] [-java <executable>(deprecated)] [-noconsole]
[-J<java-argument>]*
[-daemonhost <host>]
[-daemonport <port>]
[-daemonrmiport <port>]
[-engine <engine>]
[-groovydir <directory>]
[-ipv6]
[-javascriptdir <directory>]
[-jythondir <directory>]
[-jythonport <number>]
[-keystore <keystore file>]
[-keypass <keystore password>]
[-libpath <path>]
[-license <file>]
[-license-waitfor <seconds>]
[-logdir <directory>]
[-nolog]
[-nomessagewindow]
[-noplugins]
[-option <name>=<value>]
[-options <file>]
[-plugindir <directory>]
[-port <number>]
[-runtime]
[-serverhost <host>]
[-shell <executable>]
[-shellarg <argument>]
[-splitlog]
[-systemcfg <file>]
[-systemdir <directory>]
[-userdir <directory>]
[-variable <name>=<value>]*
qftest -batch -import
[-import-from <test suite>] [-import-into <test suite>]
[-import-components] [-import-procedures] [-import-tests]
qftest -batch -analyze
[-analyze-target <directory>]
[-suitedir <dir>]
[-analyze-references]
[-analyze-duplicates]
[-analyze-invalidchar]
[-analyze-emptynodes]
[-analyze-components]
[-analyze-procedures]
[-analyze-dependencies]
[-analyze-tests]
[-analyze-packages]
[-remove-unused-callables]
[-remove-unused-components]
[-analyze-transitive] [-analyze-followincludes]
(<suite> | <directory>)+
qftest -batch -mergelogs
[-mergelogs-mode [<mode>]]
[-mergelogs-usefqn]
[-mergelogs-resultlog [<file>]]
[-mergelogs-masterlog [<file>]]
(<run log> | <directory>)+
qftest -batch -version-allow-shutdown [<shutdown ID>])
qftest -batch -shutdown <ID> 4711
qftest -batch -interrupt-running-instances [-timeout <milliseconds>]
qftest -batch -compress <suite>+
qftest -batch -helpCommand line arguments for QF-Test fall in three categories. They can be mixed freely.
These arguments are evaluated directly by the
qftest shell script or executable and override
settings determined during installation. On Linux these settings
are stored in the file launcher.cfg in QF-Test's system
directory, on Windows the file is called launcherwin.cfg.
-batch-dbgQFTEST_DEBUG to a non-empty value. On
Windows this causes QF-Test to open a console window to display the output that would
otherwise be invisible unless the argument -noconsole is also given. This
also turns on debugging output for the qfclient and java
helper programs when using the old connection mechanism (see chapter 45).
-java <executable>(deprecated)java on Linux and javaw.exe on Windows,
unless a different value was set during installation.
This argument will be removed in a future version of QF-Test.-noconsole (Windows only)-dbg is specified.
You can pass arguments to the Java VM through the starter script
by prepending them with -J,
e.g. -J-Duser.language=en to set a system
property. To set the classpath, prepend -J only to
the -cp or -classpath argument, not to
the actual value, e.g. -J-classpath
myclasses.jar. When setting the classpath this way, QF-Test's
own jar archives need not to be taken into account.
The rest of the arguments are handled by QF-Test itself when it is
executed by the Java virtual machine. These arguments can also
be placed in a file using the syntax
<name>=<value> for arguments with
parameters or <name>=true or
<name>=false to turn a simple argument on or
off. By default this file is called qftest.options,
located in the bin directory of QF-Test and used only for internal logging
purposes. If you
change anything in this file, you can move it to QF-Test's system
directory so your changes will still apply after
upgrading. Alternatively you can use the -options <file> argument
to specify a different file. Arguments given on the command line
override arguments from an option file except for those which can
be given multiple times. In the latter case the arguments are
merged.
-allowkilling-allow-shutdown without shutdown ID instead.
-allow-shutdown [<shutdown ID>]-shutdown <ID> argument. An optional string argument can be provided as shutdown ID which allows
selective process termination without knowing the process ID. The shutdown ID must contain at least
one non-numeric character to be distinguishable from the numerical process ID. If -allow-shutdown [<shutdown ID>] has not been
specified on the command line, a running QF-Test process can only be terminated cleanly by means of the
process ID. The argument -allow-shutdown false prohibits all clean termination of the QF-Test
instance, even if -shutdown <ID> is used with the correct process ID.
-analyze (batch mode only)-analyze-target <directory> (batch mode only)-analyze-references (batch mode only)-analyze-duplicates (batch mode only)-analyze-invalidchar (batch mode only)-analyze-emptynodes (batch mode only)-analyze-components (batch mode only)-analyze-dependencies (batch mode only)-analyze-procedures (batch mode only)-analyze-tests (batch mode only)-analyze-packages (batch mode only)-remove-unused-callables (batch mode only)-remove-unused-components (batch mode only)-analyze-transitive (batch mode only)-analyze-followincludes (batch mode only)-calldaemon
(batch mode only)-cleanup
(calldaemon mode only)-clearglobals
(batch mode and calldaemon mode only)-stopclean, to clear globals after the test.
-compact (batch mode only)-nolog.
-compress (batch mode only)-convertxml (batch mode only)-convertxml-indent <number>
(convertxml mode only)-convertxml-linelength <number>
(convertxml mode only)-convertxml-utf8 <true|false>
(convertxml mode only)-daemon-daemonhost <host>
(daemon or calldaemon mode only)-daemonport <port>-port <number>.
-daemonrmiport <port>-daemonport <port>. If using SSL, two different ports are required.
-dontkillprocesses
(batch mode only)-engine <engine>-exitcode-ignore-exception
(batch and calldaemon mode)-exitcode-ignore-error
(batch and calldaemon mode)-exitcode-ignore-warning
(batch and calldaemon mode)-gendoc
(batch mode only)-genreport
(batch mode only)-groovydir <directory>groovy is located under QF-Test's system directory.
-help-import (batch mode only)-import-from <test suite> (batch mode only)-import-into <test suite> (batch mode only)-import-components (batch mode only)-import-procedures (batch mode only)-import-tests (batch mode only)-interrupt-running-instances (batch mode only)-ipv6-javascriptdir <directory>javascript is located under QF-Test's system directory.
-jythondir <directory>jython is located under QF-Test's system directory.
-jythonport <number>telnet to connect to that port and get an
interactive Jython command line.
-keybindings <value> (interactive mode only)-keystore <keystore file>-keystore=.
-keypass <keystore password>-kill-kunning-instances-shutdown all instead.
-libpath <path>include directory will automatically be appended to
the path.
-license <file>-license-waitfor <seconds>;-logdir <directory>log and located under QF-Test's system directory.
-mergelogs (batch mode only)-mergelogs-masterlog [<file>] (batch mode only)-mergelogs-mode [<mode>] (batch mode only)-mergelogs-masterlog [<file>] switch.
You can specify the modes "replace", "merge" and "append".
"replace" takes the new results and overwrites the existing test cases from the main run log.
"merge" adds the new test cases to main run log and "append" simply adds the new run log to the
main run log.
-mergelogs-resultlog [<file>] (batch mode only)-mergelogs-usefqn (batch mode only)-nolog (batch mode only)-runlog [<file>],
-report <directory>, -report-html <directory>, -report-xml <directory> or -report-junit <directory>
is given, this argument is ignored. This option is
retained for backwards compatibility only. To keep memory use manageable, split
run logs should be used instead (see -splitlog).
-nomessagewindow (batch mode only)-noplugins-noupdatecheck-option <name>=<value>-option <name>=<value>
sets a value of the option with a name
<name> to <value>.
This argument can be given more than once to set several options.
-options <file>-ping
(calldaemon mode only)-pkgdoc <directory> (batch mode only)-pkgdoc-dependencies
(batch mode only)-pkgdoc-dependencies=false to disable.
-pkgdoc-doctags=false to disable.
-pkgdoc-html <directory> (batch mode only)-pkgdoc-includelocal
(batch mode only)-pkgdoc-nodeicons
(batch mode only)-pkgdoc-nodeicons=false to disable.
-pkgdoc-passhtml
(batch mode only)-pkgdoc-passhtml=false to disable.
-pkgdoc-sortpackages
(batch mode only)-pkgdoc-sortpackages=false to disable.
-pkgdoc-sortprocedures
(batch mode only)-pkgdoc-sortprocedures=false to disable.
-pkgdoc-splitparagraph
(batch mode only)-pkgdoc-splitparagraph=false it is
possible to disable this option.
-pkgdoc-stylesheet <file>
(batch mode only)-pkgdoc-xml <directory> (batch mode only)-plugindir <directory>plugin is located under QF-Test's system directory.
See section 49.2 for more
information about plugins.
-port <number>-report <directory>
(batch mode only)-report-checks
(batch mode only)-report-customdir <directory>
(batch mode only)-report-doctags=false to disable.
-report-errors
(batch mode only)-report-errors=false to disable.
-report-exceptions
(batch mode only)-report-exceptions=false to disable.
-report-html <directory> (batch mode only)-report-ignorenotimplemented
(batch mode only)-report-ignoreskipped
(batch mode only)-report-junit <directory> (batch mode only)-report-name <name>
(batch mode only)-report-nodeicons
(batch mode only)-report-nodeicons=false to disable.
-report-passhtml
(batch mode only)-report-passhtml=false to disable.
-report-piechart
(batch mode only)-report-piechart=false to disable.
-report-include-suitename
(batch mode only)-report-include-suitename=false to use the file name instead.
-report-scale-thumbnails <percent>
(batch mode only)-report-teststeps
(batch mode only)-report-teststeps=false to disable.
-report-thumbnails
(batch mode only)-report-warnings
(batch mode only)-report-xml <directory>
(batch mode only)-reuse (interactive mode only)-run (interactive and batch mode)-runid <ID>
(batch and calldaemon mode)%i/+i.
-runlog [<file>]
(batch and calldaemon mode).qrz is added automatically and the run log is saved compressed.
Otherwise the extension .qrl or .qrz determines
compression. Even without this argument a run log is created unless suppressed with
-nolog or when a report is generated. The default value is
%p%b.qrz.
In calldaemon mode, a run log will be stored only if a (local) filename is specified.
-runlogdir <directory>-runlog [<file>] is an absolute path. If this argument is given and a report is
generated, the files in the report will be laid out according to the structure of
the run logs relative to this directory. The directory name may contain placeholders
as explained in subsection 43.2.4.
-runtime-threads <number> is given). If not enough free
runtime licenses are available, full development licenses will be used instead
unless -runtime is given in which case no development license is used and QF-Test
will fail with an error message. In interactive mode, if -runtime is given, QF-Test
will use a runtime license instead of a full development license. In that mode, any
test suite can be loaded and tests can be run interactively as usual, including
debugging support. Saving of test suites will be disabled, however, though
test suites can be modified for temporary experiments.
-shell <executable>/bin/sh, for Windows
COMMAND.COM or cmd.exe.
-shellarg <argument>-shell <executable>
to execute the following argument and then exit. For Linux shells
this is typically -c, COMMAND.COM and
cmd.exe expect /c. If you have Linux
tools installed on Windows and specify sh or
bash as the shell to use, don't forget to change
-shellarg <argument> to -c.
-shutdown <ID> (batch mode only)-allow-shutdown [<shutdown ID>]). In batch mode this means that a running test is stopped, connected
clients are terminated, the run log is saved, and the QF-Test instance terminates with the exit code -12.
If QF-Test is running interactively, all open testsuites are closed without saving modifications. In
special cases this might be useful, especially if auto-save is configured in a meaningful way (see
Auto-save interval (s)).
The special shutdown ID all terminates all running QF-Test processes that
were started with the -allow-shutdown [<shutdown ID>] argument to explicitly allow that.
-serverhost <host>-serverhost= with an empty value.
-sourcedir <directory>
(batch mode only)-runlogdir <directory> is also specified. In any case, the directory of a
test suite listed in the report will only be listed if this argument is specified
and the test suite is located below this directory.
-splitlog (batch mode only)-splitlog=false. If -splitlog is
explicitly specified without parameter, the default extension for run logs is
changed from .qrz to .qzp so as to create split run logs
in ZIP format. The same can be achieved by specifying the name of the run log
explicitly with the desired extension.
-startclean
(calldaemon mode only)-startsut
(only for internal use)qfs.qft contains
a procedure qfs.daemon.startRemoteSUT which can be use for this
purpose.
-stopclean
(calldaemon mode only)-stoprun
(calldaemon mode only)-cleanup or -stopclean.
-suitedir <dir>
(calldaemon mode only)-suitesfile <file>
(interactive and batch mode)-test <n>|<ID> argument. You can find
some samples in the table below.
| ||||||||||||||||||||
Table 43.1: Samples -suitesfile <file> | ||||||||||||||||||||
-systemcfg <file>-systemdir <directory>-systemcfg <file>,
-plugindir <directory>, -jythondir <directory>, -groovydir <directory> or -javascriptdir <directory> are also specified
they have precedence.
-tempdir <directory> (interactive mode only)TEMP and
TMP are tried.
-terminate
(calldaemon mode only)-test <n>|<ID> (interactive and batch mode)-test
<n>|<ID>, you can select specific tests. An
arbitrary node located anywhere in a test suite can be accessed
by its 'QF-Test ID'. 'Test case' or 'Test set' nodes can be
referenced also by their qualified name. Top-level tests
can also be selected by their index, the index
for the first test being 0. You can use this argument multiple
times, even for the same test.
-testdoc <directory> (batch mode only)-testdoc-doctags=false to disable.
-testdoc-followcalls
(batch mode only)-testdoc-html <directory> (batch mode only)-testdoc-nodeicons
(batch mode only)-testdoc-nodeicons=false to disable.
-testdoc-passhtml
(batch mode only)-testdoc-passhtml=false to disable.
-testdoc-sorttestcases
(batch mode only)-testdoc-sorttestcases=false to disable.
-testdoc-sorttestsets
(batch mode only)-testdoc-sorttestsets=false to disable.
-testdoc-splitparagraph
(batch mode only)-testdoc-splitparagraph=false it is
possible to disable this option.
-testdoc-stylesheet <file>
(batch mode only)-testdoc-teststeps
(batch mode only)-testdoc-teststeps=false to disable.
-testdoc-xml <directory> (batch mode only)-threads <number> (batch mode only)-runtime should be specified as well. See chapter 32 for
more information about load tests.
-timeout <milliseconds> (batch or calldaemon mode only)-usercfg <file> (interactive mode only)-userdir <directory>-usercfg <file> or -runlogdir <directory> are also specified they have
precedence.
-variable <name>=<value><name> to the value
<value>. Using this argument multiple times
you can define more than one variable.
-verbose [<level>]-calldaemon, because the actual test
usually runs on a different host where you may not be able to observe it. Note
that on Windows you need to use qftestc.exe (instead of
qftest.exe) to see the output. Specifying a level of verbosity is
optional, possible values are all (print all nodes) and
tests (default, only 'Test set' and 'Test case' nodes are
printed out). Each level can be combined with errors (print error and
exception messages) like tests,errors.
-version
The filename given in any of the command line arguments -runid <ID>,
-runlog [<file>], -runlogdir <directory>, -report <directory>, -report-html <directory>,
-report-name <name>, -report-xml <directory> or -report-junit <directory>,
may contain placeholders of the form %X or +X (the latter must
be used on Windows where '%' is a special character) where X may be any of the
characters listed in the table below. QF-Test will fill in the respective value when
creating the run log or report. All time values refer to the time the test was
started.
Note When executing multiple test suites, be sure to include the base name of the suite in the filename by specifying %b. Otherwise only a single run log or report may be written that represents only the test run of the last test suite.
| |||||||||||||||||||||||||||||||||||||||
| Table 43.2: Placeholders in filename parameters | |||||||||||||||||||||||||||||||||||||||
So if, for example, you want to save the run log in a subdirectory
of your test suite directory called logs and want to
include a timestamp and the exit code, use
-runlog %p/logs/%b-%y%M%d-%h%m%s-%r.qrl
Note It is possible to use %b, %p and %P for collective parameters like runid or report. This makes sense only when processing a single test suite. When processing multiple test suites, the name of the first test suite is used.
When run in interactive mode, the exit code of QF-Test is not very useful. It is either negative if QF-Test fails to start or 0.
In batch mode however the exit code expresses the result of the test run. Negative values represent fatal errors that prevent the test from being executed, while positive values stand for errors during the test run. Note that many systems only support exit codes between 0 and 255, so every exit code may have to be calculated modulo 256, i.e. -1=255, -2=254 and so on.
The following exit codes are currently defined:
| |||||||||||||||||||||||||||
| Table 43.3: Exit codes for QF-Test | |||||||||||||||||||||||||||
Besides, there are special exit codes when running QF-Test with the
-calldaemon argument:
| |||||||||||||||
Table 43.4: calldaemon exit codes for QF-Test | |||||||||||||||
| | | | | | | Last update: 9/10/2024 Copyright © 1999-2024 Quality First Software GmbH |
