qt6-bb10

History

Andy Shaw 1d9547c9a4 Don't indefinitely wait for data if it was able to read some data Passing -1 to waitForReadyRead() may cause it to wait for some time but the data retrieved may be enough for processing. So if 0 is passed from read, indicating that there is potentially more to come, then it will do a waitForReadyRead() then for more data to come. Change-Id: I75f270d1f124ecc12b18512cc20fb11f7a88f02e Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2018-01-24 05:54:31 +00:00
..
auto	Don't indefinitely wait for data if it was able to read some data	2018-01-24 05:54:31 +00:00
baselineserver	tests: Add Q_FALLTHROUGH to unmarked fallthroughs seen by GCC 7	2017-06-28 17:57:35 +00:00
benchmarks	Restore compatibility with pre-5.9 Keccak calculation	2017-09-21 03:21:58 +00:00
global	…
manual	Menurama: Fix custom application class constructor signature	2017-11-17 13:30:40 +00:00
shared	Fix largefile tests on ARM and QEMU targets	2017-03-28 06:55:32 +00:00
README	…
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.