qt5base-lts

History

Marius Storm-Olsen 0389278105 Only run JSC benchmarks if access to the source code When modularized, the benchmark test case might not have access to the JavaScriptCore source code. So, make sure the test case still compiles in this case.		2011-04-27 12:06:04 +02:00
..
arthur	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
auto	Remove not needed .pri include	2011-04-27 12:06:04 +02:00
benchmarks	Only run JSC benchmarks if access to the source code	2011-04-27 12:06:04 +02:00
global	Modularized tst_bic and add some helper functions for global test	2011-04-27 12:06:03 +02:00
manual	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
shared	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
README	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
tests.pro	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +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.