summaryrefslogtreecommitdiff
path: root/src/plugins/python/pythonutils.cpp
diff options
context:
space:
mode:
authorJarek Kobus <jaroslaw.kobus@qt.io>2021-04-28 15:59:18 +0200
committerJarek Kobus <jaroslaw.kobus@qt.io>2021-06-02 11:59:33 +0000
commit0f535703aa9f68e7654547ca93c118196ad2a0bd (patch)
treea5e302006f582e2b3b6ec1e7b43854e2390b4273 /src/plugins/python/pythonutils.cpp
parentff0301635e7af28df61104cc5fa15e9c407f257e (diff)
downloadqt-creator-0f535703aa9f68e7654547ca93c118196ad2a0bd.tar.gz
Implement scenario player
A scenario player may be used for testing Creator crashes which can't be easily tested with "-test <plugin>" option. Some crashes are triggered when Creator unloaded plugins and left the main function. This may happen due to some other threads may still be running. This scenario can't be tested using plugin tests, since when the test finishes, Creator still has its plugins loaded. Also it's not possible to quit Creator from inside the plugin test, as if we do it, we couldn't report the test result. The follow up patches will introduce the first test scenario and provide automatic test for testing against regression in StringTable. The scenario player may be potentially used for other purposes, including automatic presentation of features (yeah!). However, most probably the API should be further developed for other purposed. This is just a starting idea. Change-Id: I0f5c3c028f35a5cdf9130c2cf315dd4b68e81126 Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Diffstat (limited to 'src/plugins/python/pythonutils.cpp')
0 files changed, 0 insertions, 0 deletions