cppcheck/gui/test
Reijo Tomperi 5d5f7085bf Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
..
benchmark Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
data Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
filelist Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
projectfile Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
translationhandler Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
xmlreport Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
xmlreportv1 Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
xmlreportv2 Updating year 2012 -> 2013 to .cpp and .h files and man page. 2013-01-01 18:29:08 +02:00
common.pri GUITESTS: Add simple test for FileList. 2011-06-17 13:46:40 +03:00
readme.txt GUITESTS: Remove the running script. 2011-08-12 00:13:29 +03:00
test.pro BENCHMARKS: Add simple benchmark. 2011-06-22 22:24:49 +03: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.