cppcheck/gui/test
Kimmo Varis 2ef4e6fb59 GUITESTS: Remove the running script.
The script is available in another repository. I don't want to
distribute it with Cppcheck sources for now. Maybe if and when
there is more interest towards GUI tests...
2011-08-12 00:13:29 +03:00
..
benchmark run astyle 2011-06-22 20:30:41 -04:00
data BENCHMARKS: Add simple benchmark. 2011-06-22 22:24:49 +03:00
filelist GUITESTS: Add FileList filtering tests. 2011-06-18 12:54:48 +03:00
projectfile GUITESTS: Move testdata to data-subdirectory. 2011-06-17 13:56:32 +03:00
translationhandler GUITESTS: Few compares in tests were wrong way around. 2011-06-17 13:18:42 +03:00
xmlreport GUITESTS: Move testdata to data-subdirectory. 2011-06-17 13:56:32 +03:00
xmlreportv1 GUITESTS: Move testdata to data-subdirectory. 2011-06-17 13:56:32 +03:00
xmlreportv2 GUITESTS: Move testdata to data-subdirectory. 2011-06-17 13:56:32 +03: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.