qt5base-lts

History

Miikka Heikkinen ce75529968 Fix QRawFont autotest in Windows Can't use style name with Windows native font engine, so do the comparison using style in case multipleRawFontsFromData(). Also XFAILed the advances() case when using Freetype font engine in Windows, as some of the advances returned are one pixel wider than expected. Task-number: QTBUG-24197 Change-Id: Ib5fecd83a93908e57a4c82ffb5495a92474ce45a Reviewed-by: Friedemann Kleint <Friedemann.Kleint@nokia.com>		2012-04-25 22:38:45 +02:00
..
auto	Fix QRawFont autotest in Windows	2012-04-25 22:38:45 +02:00
baselineserver	baselineserver: Fix compilation by removing PI_BuildKey from the source	2012-04-25 19:52:22 +02:00
benchmarks	Replace com.trolltech with org.qtproject in D-Bus's performance tests	2012-04-22 21:32:24 +02:00
global	Modularized tst_bic and add some helper functions for global test	2011-04-27 12:06:03 +02:00
manual	lance: Document all available command line options.	2012-04-25 19:53:22 +02:00
shared	Fix MSVC warnings in tests.	2012-04-02 16:56:48 +02:00
README	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
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.