cppcheck/gui/test
Oliver Stöneberg dbc05da356
fixed some clang-tidy warnings (#4435)
2022-09-08 20:01:41 +02:00
..
benchmark use same output folder for GUI tests qmake builds to leverage existing output files from regular build (#4433) 2022-09-04 10:25:16 +02:00
cppchecklibrarydata fixed some clang-tidy warnings (#4435) 2022-09-08 20:01:41 +02:00
data fixed some `modernize-use-emplace` false negatives with `std::stack` / removed `internalStlUsage` check (#4346) 2022-08-17 09:50:14 +02:00
filelist fixed some clang-tidy warnings (#4435) 2022-09-08 20:01:41 +02:00
projectfile fixed some clang-tidy warnings (#4435) 2022-09-08 20:01:41 +02:00
translationhandler fixed some clang-tidy warnings (#4435) 2022-09-08 20:01:41 +02:00
xmlreportv2 fixed some clang-tidy warnings (#4435) 2022-09-08 20:01:41 +02:00
CMakeLists.txt added building of GUI tests to CMake (#3619) 2021-12-17 21:49:32 +01:00
common.pri Travis: Try to reactivate the gui/test tests 2019-04-19 11:57:52 +02:00
readme.txt
test.pro Travis: Try to reactivate the gui/test tests 2019-04-19 11:57:52 +02:00

readme.txt

GUI tests + benchmark tests
===========================

As the GUI uses Qt framework, the GUI tests also use Qt's Testlib. This is
totally different test framework than lib/cli is using. By principle each
testcase is compiled as an own runnable binary.

Compiling
---------

To compile all the tests run in root directory of tests:
 - qmake ; make

You can also (re)compile single test by CD:ing to the directory where test
(source) resides and running:
 - qmake ; make

Running
-------

As each test is compiled as single executable binary you can run the test just
by running the executable.

You can get from
 http://bitbucket.org/kimmov/testrun
a script which runs all the tests and collects the results.