cppcheck/gui/test
Oliver Stöneberg 5f171b9673
fixed some `modernize-use-emplace` false negatives with `std::stack` / removed `internalStlUsage` check (#4346)
2022-08-17 09:50:14 +02:00
..
benchmark Tokenizer: remove simplifyTokenList2 2022-07-18 16:20:36 +02:00
cppchecklibrarydata Library Data: Add support for optional smart pointer element 'unique' (#4132) 2022-07-04 22:23:20 +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 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 fail `run-clang-tidy` in case of compiler warnings / fixed Clang warnings / cleanups (#4036) 2022-05-15 12:42:29 +02:00
xmlreportv2 Remove bug hunting. This feature will be provided in Cppcheck premium. 2022-04-11 07:31:33 +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.