qt6-bb10

History

Alex Trotsenko bec47545dc QAbstractSocket: do not fail writing on read buffer overflow canReadNotification() could return 'false' if either the socket has been closed, or the read buffer has reached the maximum size. Because of this duality, waitForBytesWritten() should not fail as a result of a canReadNotification() call. Change-Id: I9a15fa174a3b982a7ce404913caa38fc19f64622 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@theqtcompany.com> Reviewed-by: Markus Goetz (Woboq GmbH) <markus@woboq.com>		2016-03-18 13:05:42 +00:00
..
auto	QAbstractSocket: do not fail writing on read buffer overflow	2016-03-18 13:05:42 +00:00
baselineserver	Updated license headers	2016-01-21 18:55:18 +00:00
benchmarks	Avoid qMin in format conversions when possible	2016-03-01 16:34:46 +00:00
global	…
manual	Merge remote-tracking branch 'origin/5.6' into 5.7	2016-03-11 20:08:50 +01:00
shared	Updated license headers	2016-01-21 18:55:18 +00: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.