qt5base-lts

History

Robin Burchell ecb57cfc32 Pass notification of failure of watches onto the caller. This is particularly useful for situations where the user might really want to be notified about a failure, for instance, in a backup application. Empty paths are not treated as an error in calling, as the user code cannot really do anything sensible to handle this error, but empty paths should not be used. Change-Id: Iddb44fd39f4e3fac5c3f9f60fb7999e1833280a8 Reviewed-by: João Abecasis <joao.abecasis@nokia.com> Reviewed-by: Denis Dzyubenko <denis.dzyubenko@nokia.com> Reviewed-by: Bradley T. Hughes <bradley.hughes@nokia.com>		2012-01-04 21:09:10 +01:00
..
auto	Pass notification of failure of watches onto the caller.	2012-01-04 21:09:10 +01:00
baselineserver	Add Qt's debug/release mode to the lancelot autotests' client info	2011-11-11 16:47:23 +01:00
benchmarks	Change event posting to use a QVector.	2011-12-30 21:58:10 +01:00
global
manual	Make QCocoaWindow independent of NSWindow.	2011-12-14 23:26:15 +01:00
shared	Remove SkipMode parameter from QSKIP calls.	2011-10-21 01:20:29 +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.