qt5base-lts/tests
Bradley T. Hughes 6b82798ee7 Add QFreeList as an internal class
This is a generic implementation of the lock-free free list found in
qabstracteventdispatcher.cpp. Use next() to get the next free entry in
the list, and release(id) when done with the id.

This version is templated and allows having a payload which can be
accessed using the id returned by next(). The payload is allocated and
deallocated automatically by the free list, but *NOT* when calling
next()/release(). Initialization should be done by code needing it after
next() returns. Likewise, cleanup should happen before calling
release(). It is possible to have use 'void' as the payload type, in
which case the free list only contains indexes to the next free entry.

Autotest included.

Change-Id: Ifd12a961d47f3d76593c45061f72e55c9b80a43b
Reviewed-on: http://codereview.qt.nokia.com/2160
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Olivier Goffart <olivier.goffart@nokia.com>
2011-07-26 13:40:07 +02:00
..
auto Add QFreeList as an internal class 2011-07-26 13:40:07 +02:00
baselineserver Cleaning up the QPainter/arthur testing stuff 2011-06-29 15:10:14 +02:00
benchmarks tests: do not run benchmarks by default in 'make check' 2011-07-19 13:11:37 +02:00
global Modularized tst_bic and add some helper functions for global test 2011-04-27 12:06:03 +02:00
manual Cleaning up the QPainter/arthur testing stuff 2011-06-29 15:10:14 +02:00
shared Update licenseheader text in source files for qtbase Qt module 2011-05-24 12:34:08 +03:00
README Initial import from the monolithic Qt. 2011-04-27 12:05:43 +02:00
tests.pro Don't attempt to build benchmarks if release-mode Qt is not available 2011-06-21 17:44:27 +02:00

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.