forked from qt-creator/qt-creator
ea88b32124
Fixes: QTCREATORBUG-31491 Change-Id: Ief2740b8610585a7a8722e96410060d1e0e9a7cf Reviewed-by: Cristian Adam <cristian.adam@qt.io>
29 lines
1001 B
Plaintext
29 lines
1001 B
Plaintext
See the file doc/api/coding-style.qdoc for our coding standard.
|
|
|
|
For instructions on how to set up the Qt Creator repository to contribute
|
|
patches back to Qt Creator, please check:
|
|
|
|
https://wiki.qt.io/Setting_up_Gerrit#How_to_get_started_-_Gerrit_registration
|
|
|
|
Qt Creator has integrated auto tests, and further external tests in the
|
|
subdirectory 'tests'.
|
|
|
|
To build the auto tests, manual tests and unit tests in the 'tests'
|
|
subdirectory, configure with the CMake option WITH_TESTS=ON.
|
|
|
|
Afterwards:
|
|
|
|
* The tests from the 'tests' subdirectory can be run as individual applications.
|
|
They are also available as separate Run configuration from within Qt Creator.
|
|
|
|
* All the integrated tests for a specific plugin can be run with:
|
|
|
|
qtcreator -test QtSupport
|
|
|
|
* To run only a specific test case, use:
|
|
|
|
qtcreator -test QtSupport,testQtOutputFormatter
|
|
|
|
Note: Adding -test to Qt Creator will run the tests in a clean settingspath.
|
|
To run them with specific settings, -settingspath /path has to be provided.
|