qt5base-lts

History

Shane Kearns af100dbd7e Abort background requests if policy changes to disallow them Using the policy change signal from QNetworkSession. If the new policy disallows background requests and this is a background request, then generate an error. This results in a TCP RST on the socket, and a BackgroundRequestNotAllowedError on the QNetworkReply. If the reply is already finished, no action is taken. Change-Id: I4ff5c681a8b7b852727bb95f03664d666f4efe07 Reviewed-by: Martin Petersson <Martin.Petersson@nokia.com>		2012-04-19 19:46:07 +02:00
..
auto	Abort background requests if policy changes to disallow them	2012-04-19 19:46:07 +02:00
baselineserver	Deprecate qMemCopy/qMemSet in favour of their stdlib equivilents.	2012-04-11 10:46:19 +02:00
benchmarks	Merge "Merge remote-tracking branch 'origin/master' into api_changes" into refs/staging/api_changes	2012-04-17 10:38:24 +02:00
global
manual	Add a manual test for the window geometry.	2012-04-19 19:46:07 +02:00
shared	Fix MSVC warnings in tests.	2012-04-02 16:56:48 +02:00
README
tests.pro	Re-enable the corelib autotests on Mac OS X	2011-11-21 11:31:35 +01:00

README

This directory contains autotests and benchmarks based on QTestlib. 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.