feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: Update info about code analysis tools

Browse Source 
Remove detail from the IDE Overview and Testing topics
because 7 other code analysis tools are now integrated in
addition to Valgrind and QML Profiler.

Task-number: QTCREATORBUG-28996
Change-Id: I23ab9935b9cff4f3bfc1bdc046c112dbb223c8f0
Reviewed-by: hjk <hjk@qt.io>
This commit is contained in:
Leena Miettinen
2023-06-27 15:01:45 +02:00
parent f3121a1c6b
commit 7c533d4d0c
2 changed files with 17 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
doc/qtcreator/src/overview/creator-only/creator-overview.qdoc
View File

@@ -1,4 +1,4 @@
// Copyright (C) 2021 The Qt Company Ltd. // Copyright (C) 2023 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only // SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
// ********************************************************************** // **********************************************************************
@@ -80,21 +80,18 @@
For more information, see \l{Building and Running}. For more information, see \l{Building and Running}.
\li \b {\l{Testing}} \li \b {\l{Testing}}
\QC integrates several external native debuggers: GNU \QC integrates several external native debuggers that you can use
Symbolic Debugger (GDB), Microsoft Console Debugger (CDB), and to inspect the state of your application while debugging.
internal JavaScript debugger. In the \uicontrol Debug mode, you
can inspect the state of your application while debugging.
Devices have limited memory and CPU power, so Devices have limited memory and CPU power, so you should use them
you should use them carefully. \QC integrates Valgrind code carefully. \QC integrates code analysis tools for detecting
analysis tools for detecting memory leaks and profiling function memory leaks, profiling function execution, analyzing CPU use,
execution. In addition, the QML Profiler enables you to profile and eliminating unnecessary complexity of code. Other tools
Qt Quick applications. provide code coverage and visualize trace events.
\QC integrates the \l{Qt Test}, Boost.Test, Catch 2 test, \QC integrates several testing frameworks for unit testing
and Google C++ Testing frameworks for unit testing applications applications and libraries. You can use \QC to create, build,
and libraries. You can use \QC to create, build, and run and run autotests.
autotests.
For more information, see \l{Testing}. For more information, see \l{Testing}.
\li \b {Publishing} \li \b {Publishing}

12
doc/qtcreator/src/overview/creator-only/creator-testing.qdoc
View File

@@ -1,4 +1,4 @@
// Copyright (C) 2019 The Qt Company Ltd. // Copyright (C) 2023 The Qt Company Ltd.
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only // SPDX-License-Identifier: LicenseRef-Qt-Commercial OR GFDL-1.3-no-invariants-only
// ********************************************************************** // **********************************************************************
@@ -29,11 +29,11 @@
\li \l{Analyzing Code} \li \l{Analyzing Code}
\QC integrates Valgrind code analysis tools for detecting memory Use tools for analyzing C++ and QML code to identify issues in
leaks and profiling function execution. You must download and memory management, CPU usage, coding constructs, and so on. You
install them separately to use them from \QC. The QML Profiler is must install and configure the tools on your system to use them
installed as part of \QC. It enables you to profile your Qt Quick from \QC. However, the QML Profiler is installed as part of \QC
applications. for profiling Qt Quick applications.
\li \l{Running Autotests} \li \l{Running Autotests}