Qt Test Overview
Qt Test is a framework for unit testing Qt based applications and libraries. Qt Test provides all the functionality commonly found in unit testing frameworks as well as extensions for testing graphical user interfaces.
Qt Test is designed to ease the writing of unit tests for Qt based applications and libraries:
|Lightweight||Qt Test consists of about 6000 lines of code and 60 exported symbols.|
|Self-contained||Qt Test requires only a few symbols from the Qt Core module for non-gui testing.|
|Rapid testing||Qt Test needs no special test-runners; no special registration for tests.|
|Data-driven testing||A test can be executed multiple times with different test data.|
|Basic GUI testing||Qt Test offers functionality for mouse and keyboard simulation.|
|Benchmarking||Qt Test supports benchmarking and provides several measurement back-ends.|
|IDE friendly||Qt Test outputs messages that can be interpreted by Visual Studio and KDevelop.|
|Thread-safety||The error reporting is thread safe and atomic.|
|Type-safety||Extensive use of templates prevent errors introduced by implicit type casting.|
|Easily extendable||Custom types can easily be added to the test data and test output.|
To create a test, subclass QObject and add one or more private slots to it. Each private slot is a test function in your test. QTest::qExec() can be used to execute all test functions in the test object.
In addition, there are four private slots that are not treated as test functions. They will be executed by the testing framework and can be used to initialize and clean up either the entire test or the current test function.
initTestCase()will be called before the first test function is executed.
cleanupTestCase()will be called after the last test function was executed.
init()will be called before each test function is executed.
cleanup()will be called after every test function.
initTestCase() fails, no test function will be executed. If
init() fails, the following test function will not be executed, the test will proceed to the next test function.
For more examples, refer to the Qt Test Tutorial.
If you are using
qmake as your build tool, just add the following to your project file:
QT += testlib
If you would like to run the test via
make check, add the additional line:
CONFIG += testcase
See the qmake manual for more information about
If you are using other build tools, make sure that you add the location of the Qt Test header files to your include path (usually
include/QtTest under your Qt installation directory). If you are using a release build of Qt, link your test to the
QtTest library. For debug builds, use
See Writing a Unit Test for a step by step explanation.
The syntax to execute an autotest takes the following simple form:
testname [options] [testfunctions[:testdata]]...
testname with the name of your executable.
testfunctions can contain names of test functions to be executed. If no
testfunctions are passed, all tests are run. If you append the name of an entry in
testdata, the test function will be run only with that test data.
/myTestDirectory$ testQString toUpper
Runs the test function called
toUpper with all available test data.
/myTestDirectory$ testQString toUpper toInt:zero
toUpper test function with all available test data, and the
toInt test function with the test data called
zero (if the specified test data doesn't exist, the associated test will fail).
/myTestDirectory$ testMyWidget -vs -eventdelay 500
testMyWidget function test, outputs every signal emission and waits 500 milliseconds after each simulated mouse/keyboard event.
The following command line options determine how test results are reported:
Writes output to the specified file, in the specified format (one of
xunitxml). The special filename
-may be used to log to standard output.
Writes output to the specified file.
Outputs results in plain text.
Outputs results as an XML document.
Outputs results as a stream of XML tags.
Outputs results as an Xunit XML document.
Outputs results as comma-separated values (CSV). This mode is only suitable for benchmarks, since it suppresses normal pass/fail messages.
Outputs results in TeamCity format.
The first version of the
-o option may be repeated in order to log test results in multiple formats, but no more than one instance of this option can log test results to standard output.
If the first version of the
-o option is used, neither the second version of the
-o option nor the
-xunitxml options should be used.
If neither version of the
-o option is used, test results will be logged to standard output. If no format option is used, test results will be logged in plain text.
The following command line options control how much detail is reported in test logs:
Silent output; only shows fatal errors, test failures and minimal status messages.
Verbose output; shows when each test function is entered. (This option only affects plain text output.)
Extended verbose output; shows each QCOMPARE() and QVERIFY(). (This option affects all output formats and implies
-v1for plain text output.)
Shows all signals that get emitted and the slot invocations resulting from those signals. (This option affects all output formats.)
The following command-line options influence how tests are run:
Outputs all test functions available in the test, then quits.
Outputs all data tags available in the test. A global data tag is preceded by ' __global__ '.
If no delay is specified for keyboard or mouse simulation (QTest::keyClick(), QTest::mouseClick() etc.), the value from this parameter (in milliseconds) is substituted.
Like -eventdelay, but only influences keyboard simulation and not mouse simulation.
Like -eventdelay, but only influences mouse simulation and not keyboard simulation.
Sets the maximum number of warnings to output. 0 for unlimited, defaults to 2000.
Disables the crash handler on Unix platforms. On Windows, it re-enables the Windows Error Reporting dialog, which is turned off by default. This is useful for debugging crashes.
This command line argument applies to all Qt applications, but might be especially useful in the context of auto-testing. By using the "offscreen" platform plugin (-platform offscreen) it's possible to have tests that use QWidget or QWindow run without showing anything on the screen. Currently the offscreen platform plugin is only fully supported on X11.
The following command line options control benchmark testing:
Uses Callgrind to time benchmarks (Linux only).
Uses CPU tick counters to time benchmarks.
Counts events received during benchmarks.
Sets the minimum acceptable measurement value.
Sets the minimum acceptable total for repeated executions of a test function.
Sets the number of accumulation iterations.
Sets the number of median iterations.
Outputs verbose benchmarking information.
Outputs the possible command line arguments and gives some useful help.
To create a benchmark, follow the instructions for creating a test and then add a QBENCHMARK macro to the test function that you want to benchmark.
The code inside the QBENCHMARK macro will be measured, and possibly also repeated several times in order to get an accurate measurement. This depends on the selected measurement back-end. Several back-ends are available. They can be selected on the command line:
|CPU tick counter||-tickcounter||Windows, macOS, Linux, many UNIX-like systems.|
|Event Counter||-eventcounter||All platforms|
|Valgrind Callgrind||-callgrind||Linux (if installed)|
In short, walltime is always available but requires many repetitions to get a useful result. Tick counters are usually available and can provide results with fewer repetitions, but can be susceptible to CPU frequency scaling issues. Valgrind provides exact results, but does not take I/O waits into account, and is only available on a limited number of platforms. Event counting is available on all platforms and it provides the number of events that were received by the event loop before they are sent to their corresponding targets (this might include non-Qt events).
The Linux Performance Monitoring solution is available only on Linux and provides many different counters, which can be selected by passing an additional option
-perfcounter countername, such as
-perfcounter branch-misses, or
-perfcounter l1d-load-misses. The default counter is
cpu-cycles. The full list of counters can be obtained by running any benchmark executable with the option
- Using the performance counter may require enabling access to non-privileged applications.
- Devices that do not support high-resolution timers default to one-millisecond granularity.
See Writing a Benchmark in the Qt Test Tutorial for more benchmarking examples.
© 2019 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.