qt6-bb10

History

Thiago Macieira 84fcc38955 Autotest: when using libproxy, QNetworkProxyFactory isn't generic Looks like whoever created the blacklist never tried to figure out why it happened. Change-Id: I84e45059a888497fb55ffffd14d2fb29e32a4521 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>		2017-09-13 18:42:44 +00:00
..
auto	Autotest: when using libproxy, QNetworkProxyFactory isn't generic	2017-09-13 18:42:44 +00:00
baselineserver	tests: Add Q_FALLTHROUGH to unmarked fallthroughs seen by GCC 7	2017-06-28 17:57:35 +00:00
benchmarks	Remove QMAKE_LIBS_NETWORK from QSqlQuery benchmark	2017-08-28 13:10:34 +00:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	macOS: Fix padding around tab label with icon	2017-08-18 07:27:52 +00:00
shared	Fix largefile tests on ARM and QEMU targets	2017-03-28 06:55:32 +00:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro	Build examples and tests only if their requirements are met	2017-03-22 15:55:55 +00:00

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.