Grouping of test cases can now get enabled for each
registered framework.
For now grouping happens only folder based.
Task-number: QTCREATORBUG-17979
Change-Id: Ic0e5c0ecc76998a1aedea8aa0845f6d9b53fb179
Reviewed-by: David Schulz <david.schulz@qt.io>
We might find some test constructs that cannot get run
without further knowledge which should be provided by the
user (e.g. plugin unit tests of QC)
Omit these tests to avoid user irritation and useless
warnings.
Change-Id: Ia8f533b931a7c58bd768697c0915cbdd44225534
Reviewed-by: David Schulz <david.schulz@qt.io>
Adding the possibility to trigger menu actions from the locator
Change-Id: I70d595c167f5b43b02f8125eafbb83e5b45012c9
Reviewed-by: André Hartmann <aha_1980@gmx.de>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
$$PWD and $$OUT_PWD are the same for in-source builds, so rename the
source Info.plist to avoid overwriting it with the same name (which
could easily lead to an accidental git submit of the generated file).
Change-Id: Idc593d8e00dc52f11309eae3b913799fb9b8afdf
Reviewed-by: Christian Kandeler <christian.kandeler@qt.io>
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
We get more and more actions and notifying those slowly
becomes a bottleneck.
I guess we have to add an enum to the context
that tells the action which notifier on the view was called,
so that the action only react to relevant notifiers.
Change-Id: Ic05999b5855e4823659ff1520484242e0c957f1e
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
This is just a minimal workaround for dark themes.
Change-Id: I11de88dd39f24bd4d09a1c955e27a140eaad3850
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Only qmake requires the build directory to be at the same level as the
source directory, but the warning appeared also for cmake and qbs
projects.
Change-Id: I2c2c39b0a6004bb4efe80bf6ff56c3f9e22ec51d
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Change-Id: I9107356d52bbf6d1e77b30d7057b56efd670c724
Reviewed-by: André Hartmann <aha_1980@gmx.de>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
That's what it is documented to be: It is set up from a
BuildTargetInfo::targetName containing the .pro file name.
Change-Id: Iabd1061960897125e1b09902d55661d42f481e26
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
... if separate debug info is enabled.
Change-Id: I15a02b11e7df18719074b9bc503fe2c207f8bf00
Reviewed-by: Jake Petroules <jake.petroules@qt.io>
Reviewed-by: Alexandru Croitor <alexandru.croitor@qt.io>
...and make the scrollbar look the same as the scrollbars in the
QtQuickViews.
Change-Id: I15cd5a7f34efc744b74d6db2322b1aa084d09511
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
It wasn't really a singleton even before. For testing purposes make the
client/state/model managers accessible.
Change-Id: Ie5efbc47a6b9119495f999e4e05877d4789da407
Reviewed-by: hjk <hjk@qt.io>
The build list names are always the ones determined from the
build list id. No need to do that on the caller side.
Change-Id: Icc21ef355de535af21215819fe04daa76fed0d9c
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
Fixup after 45d6a34f: An empty list of target device restrictions
means 'no restriction'.
Change-Id: I15773e75e58c3ba543d62e13d728cf08dccc3650
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
These paths are controlled by ICore.
Add ICore::installerResourcePath() to replace constructions with
settings(SystemScope)
Replace constructions with settings()->fileName() by usage of
ICore::userResourcePath().
Change-Id: I5a9fa9d09f2563c39dc5d11a4586da825c62f9ac
Reviewed-by: Tobias Hunger <tobias.hunger@qt.io>
The missing headers were included indirectly
through the QHeaderView, QButtonGroup or QAction
inside the generated ui files.
Now, the generated ui files won't include QHeaderView,
QButtonGroup nor QAction, so we need to include the
missing headers explicitly.
Change-Id: Ife6c4e2c39b2b2b7d8365cc5ae2dbb6de4b3ac66
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
This one helps to understand when and why some jobs run.
Change-Id: Ibbafe517cb38bb9b68b73c78aaba0805f11b3964
Reviewed-by: Ivan Donchevskii <ivan.donchevskii@qt.io>
If the model manager or the state manager disappear before the parent
widget, we might still get a timer update in between.
Change-Id: I6a67868615ef9d570e2ce438d9d9bd88b1035cc2
Reviewed-by: hjk <hjk@qt.io>
