4449dbe737
Blacklisting items on the baseline server would avoid any mismatch failures for such items. However, they would still be rendered. That is undesirable if the rendering itself has unwanted side effects for such items, e.g. crashing the test executable. Fix by adding new functionality in the baseline testing framework to allow checking blacklisting status ahead of time, and add a new macro QBASELINE_SKIP_IF_BLACKLISTED to do just that. Add usage of that macro to the QPainter baseline test. Pick-to: 6.7 6.5 6.2 Change-Id: I35f6df8cff2c6cb985c25ab5470cd42b53d44940 Reviewed-by: Eskil Abrahamsen Blomfeldt <eskil.abrahamsen-blomfeldt@qt.io> |
||
|---|---|---|
| .. | ||
| auto | ||
| baseline | ||
| benchmarks | ||
| global | ||
| libfuzzer | ||
| manual | ||
| shared | ||
| testserver | ||
| CMakeLists.txt | ||
| README | ||
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.