qt5base-lts

History

Thiago Macieira 33371c016e Add unit testing for the qdbusxml2cpp tool I have not added tests for warnings or other failure to input. This tests only proper output for the moment. Change-Id: Ie01fd2a78adfa57c27bf288a08cd44ae82f51241 Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>		2012-04-21 01:18:56 +02:00
..
auto	Add unit testing for the qdbusxml2cpp tool	2012-04-21 01:18:56 +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	Modularized tst_bic and add some helper functions for global test	2011-04-27 12:06:03 +02:00
manual	Merge remote-tracking branch 'origin/master' into api_changes	2012-04-16 12:04:34 +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.