Category:Tools::QtCreator::QualityAssurance: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
No edit summary
 
(Avoid self-referential category; make sub-category of its natural parent.)
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
=Qt Creator Quality Assurance=
[[Category:Tools::QtCreator]]


==Auto Tests==
= Qt Creator Quality Assurance =


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 /> and<br /> afterwards. If you’re using shadow-builds you must pass the ''<span class="caps">IDE</span>_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 /> to compile ignoring potential errors. All auto test executables can be found afterwards inside their respective folders named ‘tst_*’ (or ‘tst_*.exe’ on Windows).
== Auto Tests ==


==Plugin 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
<code>qmake -r CONFIG+=debug QTCREATOR_REPOSITORY/tests/auto/auto.pro
</code>
and
<code>make
</code>
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
<code>make -i
</code>
to compile ignoring potential errors. All auto test executables can be found afterwards inside their respective folders named 'tst_*' (or 'tst_*.exe' on Windows).


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 ''<span class="caps">PLUGINNAME</span>''[,''<span class="caps">TESTFUNCTION</span>''[:''<span class="caps">TESTDATA</span>'']]…’ with ''<span class="caps">PLUGINNAME</span>'' replaced by the plugin you want to test. ''<span class="caps">TESTFUNCTION</span>'' might contain wildcard characters. If ''<span class="caps">TESTDATA</span>'' is specified, it will be applied to all matching test functions.
== Plugin Tests ==


Not every plugin provides integrated plugin unit tests – 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.
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.


==Squish Tests==
Not every plugin provides integrated plugin unit tests - 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.


Qt Creator is being tested using [http://www.froglogic.com/squish/gui-testing/index.php Squish by Froglogic] ''[froglogic.com]''. You can find the scripts in tests/system of Qt Creator’s git repository. See the [http://qt.gitorious.org/qt-creator/qt-creator/blobs/master/tests/system/README <span class="caps">README</span>] ''[qt.gitorious.org]'' on how to run them.
== Squish Tests ==


==Manual Testing==
Qt Creator is being tested using [http://www.froglogic.com/squish/gui-testing/index.php Squish by Froglogic]. You can find the scripts in tests/system of Qt Creator's git repository. See the [https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/tests/system/README README] on how to run them.


[[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 <span class="caps">MSVC</span>/cdb]]<br />[[Qt Creator ManualTests DebuggerLldb|Debugger lldb]]<br />[[Qt Creator ManualTests QtQuick|Qt Quick]]<br />[[Qt Creator ManualTests Android|Android]]<br />[[Qt Creator ManualTests iOS|iOS]]
== Manual Testing ==


===There are 11 articles in "Tools -&gt; QtCreator -&gt; QualityAssurance":===
[[Qt_Creator_ManualTests_Installer|Installer]]<br/>
 
[[Qt_Creator_ManualTests_ProjectsAndCode|Projects and Code]]<br/>
===Q===
[[Qt_Creator_ManualTests_ToolsIntegration|Tools Integration]]<br/>
* [[Qt Creator ManualTests Android|Qt_Creator_ManualTests_Android]]
[[Qt_Creator_ManualTests_DebuggerGdb|Debugger g++/gdb]]<br/>
* [[Qt Creator ManualTests DebuggerCdb|Qt_Creator_ManualTests_DebuggerCdb]]
[[Qt_Creator_ManualTests_DebuggerCdb|Debugger MSVC/cdb]]<br/>
* [[Qt Creator ManualTests DebuggerGdb|Qt_Creator_ManualTests_DebuggerGdb]]
[[Qt_Creator_ManualTests_DebuggerLldb|Debugger lldb]]<br/>
* [[Qt Creator ManualTests DebuggerLldb|Qt_Creator_ManualTests_DebuggerLldb]]
[[Qt_Creator_ManualTests_QtQuick|Qt Quick]]<br/>
* [[Qt Creator ManualTests Installer|Qt_Creator_ManualTests_Installer]]
[[Qt_Creator_ManualTests_Android|Android]]<br/>
* [[Qt Creator ManualTests iOS|Qt_Creator_ManualTests_iOS]]
[[Qt Creator ManualTests iOS|iOS]]<br/>
* [[Qt Creator ManualTests ProjectsAndCode|Qt_Creator_ManualTests_ProjectsAndCode]]
* [[Qt Creator ManualTests QtQuick|Qt_Creator_ManualTests_QtQuick]]
* [[Qt Creator ManualTests ToolsIntegration|Qt_Creator_ManualTests_ToolsIntegration]]===T===
* [[:Category:Tools::QtCreator|Category:Tools -&gt; QtCreator]]
* [[:Category:Tools::QtCreator::QualityAssurance|Category:Tools -&gt; QtCreator -&gt; QualityAssurance]]
 
===Categories:===
 
* [[:Category:Tools|Tools]]
** [[:Category:Tools::QtCreator|QtCreator]]
* [[:Category:Tools::QtCreator::QualityAssurance|QualityAssurance]]

Latest revision as of 13:49, 21 September 2016


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

and 

make

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

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.

Not every plugin provides integrated plugin unit tests - 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. You can find the scripts in tests/system of Qt Creator's git repository. See the 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
iOS

Retrieved from "https://wiki.qt.io/index.php?title=Category:Tools::QtCreator::QualityAssurance&oldid=28490"