cppcheck/gui/test
Lauri Nurmi 1cc872f5b2 Change "obsolete" in all filenames into "obsolescent", and also update all references to such files.
Neither the C standard, the C++ standard, or POSIX talks about "obsolete". All of them use the word "obsolescent", which is a different word with a different meaning.
2014-09-23 16:18:04 +02:00
..
benchmark Update copyright 2014-02-15 07:45:39 +01:00
data Change "obsolete" in all filenames into "obsolescent", and also update all references to such files. 2014-09-23 16:18:04 +02:00
filelist Update copyright 2014-02-15 07:45:39 +01:00
projectfile Update copyright 2014-02-15 07:45:39 +01:00
translationhandler Update copyright 2014-02-15 07:45:39 +01:00
xmlreport Update copyright 2014-02-15 07:45:39 +01:00
xmlreportv1 Update copyright 2014-02-15 07:45:39 +01:00
xmlreportv2 Update copyright 2014-02-15 07:45:39 +01:00
common.pri
readme.txt
test.pro

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.