cded6afa35
Some zones that fell into one or another of the supported groups had different start times or even dates for their transitions, causing the tests to fail in those zones. Adapt the test data to them. In the process, arrange for part of the test to report more: verifying a value is 1 or -1 sadly leaves no report of what it was when it wasn't. So use the scope-guard report pattern to do that on failure. Change-Id: I01cc4a90e3b45867ba0edb2d6c46397d465046ff Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> |
||
---|---|---|
.. | ||
auto | ||
baseline | ||
benchmarks | ||
global | ||
libfuzzer | ||
manual | ||
shared | ||
testserver | ||
CMakeLists.txt | ||
README |
This directory contains autotests and benchmarks based on Qt Test. 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.