Qt Creator ManualTests QtQuick: Difference between revisions
Jump to navigation
Jump to search
m (typo) |
(Update: QML errors can appear at compile time or at run time) |
||
(One intermediate revision by the same user not shown) | |||
Line 44: | Line 44: | ||
|Drag&Drop elements around in outline, check that text updates | |Drag&Drop elements around in outline, check that text updates | ||
| | | | ||
| | |Has been broken for a while. If it works again, please comment on [https://bugreports.qt.io/browse/QTCREATORBUG-26391 QTCREATORBUG-26391]. | ||
|+ | |+ | ||
|Check/Uncheck 'Show all Bindings' in the Filter, outline should update accordingly | |Check/Uncheck 'Show all Bindings' in the Filter, outline should update accordingly | ||
Line 145: | Line 145: | ||
#Run the project on the desktop. | #Run the project on the desktop. | ||
Are the error messages in Application Output clickable when running the app? Do they open the "right", file (in the source directory)? | Are the error messages in "Issues" or "Application Output", respectively, clickable when running the app? Do they open the "right", file (in the source directory)? | ||
| | | | ||
| | | |
Latest revision as of 11:47, 12 March 2024
Test | Result | Annotation |
---|---|---|
Open Qml files, make them invalid & again valid, check that errors are underlined | ||
Indent a big Qml file via "Ctrl-I" | automated | |
Hover over elements, properties, expressions | automated | |
Rename an ID via context menu | automated | |
Trigger Find Usages on an id and property | automated |
Test | Result | Annotation |
---|---|---|
Navigate to elements / properties by clicking on the item in the outline | ||
Change qml in text, check that Outline updates | automated: tst_qml_outline | |
Drag&Drop elements around in outline, check that text updates | Has been broken for a while. If it works again, please comment on QTCREATORBUG-26391. | |
Check/Uncheck 'Show all Bindings' in the Filter, outline should update accordingly |
Test | Result | Annotation |
---|---|---|
Create new "Qt Quick Application" through wizard, run application | automated | |
Create new "Qt Quick Application (compat)" through wizard, run application | ||
Create new "Qt Quick UI Prototype" through wizard, run application | automated | |
Generate "Qt Quick 2 Extension Plugin", compile | automated |
Test | Result | Annotation |
---|---|---|
Preparation:
|
||
Check that the breakpoint is being hit when clicking on "1 Player", and that the breakpoint loses it's 'hour glass' when hit. | ||
Step through startNewGame() function. Check Locals and Expressions update. Also try adding Expression Evaluators, and change content in Locals and Expressions. | ||
Add breakpoint while debugging QML. Does the breakpoint interrupt the program? | ||
Add breakpoint before starting QML Debugger. Does the breakpoint interrupt the program? | ||
While interrupted in a javascript method (with more than one line), step over. Does it go to the next line? | ||
While interrupted in a javascript method that calls another javascript method, step into. Does it enter that method's definition? | ||
While interrupted in a javascript method, step out. Does execution resume again (or does debugger go back in context)? |
Test | Result | Annotation |
---|---|---|
Breakpoints:
Are breakpoints being hit? Do they open the right file, i.e. the one in the source directory? |
||
With the project from the previous test:
Are the error messages in "Issues" or "Application Output", respectively, clickable when running the app? Do they open the "right", file (in the source directory)? |
||
Breakpoints in bigger project:
|
Test | Result | Annotation |
---|---|---|
Can you record some profiling data (see below)? | ||
Do all tabs show well-formed data/information for the shown events? | ||
Can you turn on and off the tabs by using the context menu and do all (re-)shown tabs still show well-formed data according to the last profiling? | ||
With and without an already profiled app disable profiling by hitting the record button and start running again. Does the widget 's content still hold the data of the former profiling (or none if there wasn't any)? | ||
Start a new analysis and test the record button. It should show the collected data when disabled, and collect new data on already running application when enabled. | ||
According to the Timeline tab:
(Note: The little titled subwindows in the timeline are called "tool tip" below, even though they don't behave like normal tooltips.)
|
||
According to the Statistics tab:
|
||
On the Flame Graph tab:
|
Recording Profiling Data
Create or open a project. To record data:
- Enable QML debugging in the Projects mode (might require rebuilding the app)
- Switch to Debug mode, QML Profiler view and press the "Start" button at the QML Profiler view
- Generate some events by playing around in the running application
- Press "Stop" at the QML Profiler view
Try if this works with a Qt Quick Application as well as with a Qml Project. samegame.pro and samegame.qmlproject should be adequate. They are in qtdoc/examples/demos/samegame