cppcheck/gui/test
Oliver Stöneberg 2b3fc5ed1a
replaced Qt `foreach()` with standard `for` range loop / some related cleanups (#3915)
* replaced Qt foreach() with standard for range loop / some related cleanups

* updated translations
2022-03-21 17:14:26 +01:00
..
benchmark Replace tinyxml2_LIBRARY with tinyxml2_LIBRARIES (#3897) 2022-03-15 21:17:03 +01:00
cppchecklibrarydata avoid some Clang compiler warnings (#3896) 2022-03-13 20:07:58 +01:00
data more copyright fixes (#3771) 2022-01-28 18:30:12 +01:00
filelist avoid some Clang compiler warnings (#3896) 2022-03-13 20:07:58 +01:00
projectfile avoid some Clang compiler warnings (#3896) 2022-03-13 20:07:58 +01:00
translationhandler replaced Qt `foreach()` with standard `for` range loop / some related cleanups (#3915) 2022-03-21 17:14:26 +01:00
xmlreportv2 Replace tinyxml2_LIBRARY with tinyxml2_LIBRARIES (#3897) 2022-03-15 21:17:03 +01: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.