qt5base-lts

History

Christian Ehrlicher 03b1d2c449 QColor: unify behavior when passing invalid values to setFoo() Calling QColor::setFoo() is currently inconsistent - some setter do invalidate the colors, some don't. Unify it by calling invalidate in every setter. Task-number: QTBUG-62452 Change-Id: Ia4f0bd16ea30e9659bc989ffc2b319892438b84b Reviewed-by: André Hartmann <aha_1980@gmx.de> Reviewed-by: Allan Sandfeld Jensen <allan.jensen@qt.io>		2019-11-22 22:22:17 +01:00
..
auto	QColor: unify behavior when passing invalid values to setFoo()	2019-11-22 22:22:17 +01:00
baselineserver	Merge remote-tracking branch 'origin/5.13' into 5.14	2019-09-09 07:51:49 +00:00
benchmarks	Get rid of QT_STRICT_ITERATORS	2019-11-04 12:52:26 +00:00
global
libfuzzer	Fuzzing: Don't copy input data to QByteArray	2019-10-09 17:16:09 +02:00
manual	Fix two manual tests qmake project files	2019-11-13 15:00:58 +01:00
shared	Remove usages of Q_OS_WINCE	2019-05-23 13:51:05 +02:00
testserver	Share the common configurations among different modules	2019-07-01 01:09:42 +02:00
README
tests.pro

README

This directory contains autotests and benchmarks based on Qt Test. In order
to run the autotests reliably, you need to configure a desktop to match the
test environment that these tests are written for.

Linux X11:

   * The user must be logged in to an active desktop; you can't run the
     autotests without a valid DISPLAY that allows X11 connections.

   * The tests are run against a KDE3 or KDE4 desktop.

   * Window manager uses "click to focus", and not "focus follows mouse". Many
     tests move the mouse cursor around and expect this to not affect focus
     and activation.

   * Disable "click to activate", i.e., when a window is opened, the window
     manager should automatically activate it (give it input focus) and not
     wait for the user to click the window.