qt5base-lts

History

Thiago Macieira fbabbe63c5 Use UTF-8 in the QtTest data and benchmark tags Future-proofing. Since Qt source code is now mandated to be in UTF-8, it is entirely possible that someone will use non-ASCII in data tags. Though it would be interesting to see how to access them from the Windows command-line. Change-Id: I880fc312432b62143888ff1e1d9abbd54f704601 Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>		2012-06-09 10:45:01 +02:00
..
auto	Use UTF-8 in the QtTest data and benchmark tags	2012-06-09 10:45:01 +02:00
baselineserver	baselineserver: Fix compilation by removing PI_BuildKey from the source	2012-04-25 19:52:22 +02:00
benchmarks	Implement QVector with QArrayData interface.	2012-05-30 17:07:27 +02:00
global
manual	Add Qt::WindowTransparentForInput to Window flags manual test.	2012-06-08 08:02:46 +02:00
shared	Fix MSVC warnings in tests.	2012-04-02 16:56:48 +02:00
README
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 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.