Category:Tools::QtCreator::QualityAssurance: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Category:Tools::QtCreator::QualityAssurance]] | |||
== | [toc align_right="yes" depth="2"] | ||
= Qt Creator Quality Assurance = | |||
== | == Auto Tests == | ||
Qt | Qt Creator's auto tests are actually executed internally only, but you can run them for yourself as well. You can find the auto tests in tests/auto of Qt Creator's git repository. To run them you need to compile Qt Creator first. It's recommended to use a debug build (for Qt Creator as well as for the auto tests), but you should be able to get most of the tests run on a release build as well.<br />Compile the auto tests by running<br /><code>qmake -r CONFIG+=debug QTCREATOR_REPOSITORY/tests/auto/auto.pro<br /></code><br />and<br /><code>make<br /></code><br />afterwards. If you're using shadow-builds you must pass the ''IDE_BUILD_TREE'' variable pointing to the build directory of your Qt Creator build to the qmake call.<br />Sometimes it is wise to use<br /><code>make -i<br /></code><br />to compile ignoring potential errors. All auto test executables can be found afterwards inside their respective folders named 'tst_'''' (or 'tst_'''.exe' on Windows). | ||
== Plugin Tests == | |||
Qt Creator's plugin unit tests are integrated into the source code of the respective plugins. To execute the plugin tests you'll need a debug build of Qt Creator. After finished compiling you just start Qt Creator with the option '-test all' or '<s>test ''PLUGINNAME''[,''TESTFUNCTION''[:''TESTDATA'']]…' with ''PLUGINNAME'' replaced by the plugin you want to test. ''TESTFUNCTION'' might contain wildcard characters. If ''TESTDATA'' is specified, it will be applied to all matching test functions. | |||
<br />Not every plugin provides integrated plugin unit tests</s> so for the first time run it might be a good idea to run all tests to figure out which plugin names you can use. If you want to figure out by yourself whether a plugin has tests or not check the pluginspec files inside lib/qtcreator/plugins/QtProject of Qt Creator's repository to get the plugin name you can use for the '-test' option. | |||
== Squish Tests == | |||
Qt Creator is being tested using "Squish by Froglogic&quot;:http://www.froglogic.com/squish/gui-testing/index.php. You can find the scripts in tests/system of Qt Creator's git repository. See the "README&quot;:http://qt.gitorious.org/qt-creator/qt-creator/blobs/master/tests/system/README on how to run them. | |||
== Manual Testing == | |||
[[Qt_Creator_ManualTests_Installer|Installer]]<br />[[Qt_Creator_ManualTests_ProjectsAndCode|Projects and Code]]<br />[[Qt_Creator_ManualTests_ToolsIntegration|Tools Integration]]<br />[[Qt_Creator_ManualTests_DebuggerGdb|Debugger g++/gdb]]<br />[[Qt_Creator_ManualTests_DebuggerCdb|Debugger MSVC/cdb]]<br />[[Qt_Creator_ManualTests_DebuggerLldb|Debugger lldb]]<br />[[Qt_Creator_ManualTests_QtQuick|Qt Quick]]<br />[[Qt_Creator_ManualTests_Android|Android]] | |||
Revision as of 09:52, 24 February 2015
[toc align_right="yes" depth="2"]
Qt Creator Quality Assurance
Auto Tests
Qt Creator's auto tests are actually executed internally only, but you can run them for yourself as well. You can find the auto tests in tests/auto of Qt Creator's git repository. To run them you need to compile Qt Creator first. It's recommended to use a debug build (for Qt Creator as well as for the auto tests), but you should be able to get most of the tests run on a release build as well.
Compile the auto tests by running
qmake -r CONFIG+=debug QTCREATOR_REPOSITORY/tests/auto/auto.pro<br />
and
make<br />
afterwards. If you're using shadow-builds you must pass the IDE_BUILD_TREE variable pointing to the build directory of your Qt Creator build to the qmake call.
Sometimes it is wise to use
make -i<br />
to compile ignoring potential errors. All auto test executables can be found afterwards inside their respective folders named 'tst_' (or 'tst_.exe' on Windows).
Plugin Tests
Qt Creator's plugin unit tests are integrated into the source code of the respective plugins. To execute the plugin tests you'll need a debug build of Qt Creator. After finished compiling you just start Qt Creator with the option '-test all' or 'test PLUGINNAME[,TESTFUNCTION[:TESTDATA]]…' with PLUGINNAME replaced by the plugin you want to test. TESTFUNCTION might contain wildcard characters. If TESTDATA is specified, it will be applied to all matching test functions.
so for the first time run it might be a good idea to run all tests to figure out which plugin names you can use. If you want to figure out by yourself whether a plugin has tests or not check the pluginspec files inside lib/qtcreator/plugins/QtProject of Qt Creator's repository to get the plugin name you can use for the '-test' option.
Not every plugin provides integrated plugin unit tests
Squish Tests
Qt Creator is being tested using "Squish by Froglogic":http://www.froglogic.com/squish/gui-testing/index.php. You can find the scripts in tests/system of Qt Creator's git repository. See the "README":http://qt.gitorious.org/qt-creator/qt-creator/blobs/master/tests/system/README on how to run them.
Manual Testing
Installer
Projects and Code
Tools Integration
Debugger g++/gdb
Debugger MSVC/cdb
Debugger lldb
Qt Quick
Android
Pages in category "Tools::QtCreator::QualityAssurance"
The following 9 pages are in this category, out of 9 total.
Q
- Qt Creator ManualTests Android
- Qt Creator ManualTests DebuggerCdb
- Qt Creator ManualTests DebuggerGdb
- Qt Creator ManualTests DebuggerLldb
- Qt Creator ManualTests Installer
- Qt Creator ManualTests iOS
- Qt Creator ManualTests ProjectsAndCode
- Qt Creator ManualTests QtQuick
- Qt Creator ManualTests ToolsIntegration