qt5base-lts

History

Mårten Nordheim 2dfa41e0ea Return to eventloop after emitting encrypted When the connection has been encrypted we will, in QHttpNetworkConnectionChannel::_q_encrypted, emit 'reply->encrypted' in which user slots can be called. In the event that the user calls abort it will, however, not abort until the next time it goes back to the event loop (which might not happen until after the request has already been sent). Task-number: QTBUG-65960 Change-Id: I96865f83c47f89deb9f644c86a71948dbb0ec0d0 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>		2018-07-31 14:57:02 +00:00
..
auto	Return to eventloop after emitting encrypted	2018-07-31 14:57:02 +00:00
baselineserver	Allow QImage with more than 2GByte of image data	2017-07-08 08:17:13 +00:00
benchmarks	tst_bench_QUuid: eliminate an unused variable	2018-06-14 09:15:06 +00:00
global
manual	Show the toolbutton's menu in the right place on multiple screens	2018-07-10 15:24:16 +00:00
shared	tests: Include QFileInfo in emulationdetector.h	2018-05-14 12:36:28 +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.