qt5base-lts

History

Tomasz Olszak 3867bc5a10 Send DynamicPropertyChange event only when value is changed. According to docs DynamicPropertyChange event should be sent from setProperty function only when property is added, removed or changed. Change-Id: I080a27a4119a63580b03172f4b5b367338c6f440 Reviewed-by: Olivier Goffart <ogoffart@woboq.com>		2014-01-09 12:14:42 +01:00
..
auto	Send DynamicPropertyChange event only when value is changed.	2014-01-09 12:14:42 +01:00
baselineserver	WinRT: Fix various test compilations	2013-10-02 12:36:05 +02:00
benchmarks	WinRT: Fixed compilation of network autotests and benchmarks	2013-12-06 15:06:47 +01:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
manual	Merge remote-tracking branch 'origin/stable' into dev	2013-12-16 16:59:33 +01:00
shared	WinRT: Fix various test compilations	2013-10-02 12:36:05 +02:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro	Properly implement a 'make docs' target for subdirs and apps/libs	2012-05-09 08:34:42 +02: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.