0e96dd3464
Between the find() == 0 obfuscation (since fixed) and this unchecked replace(), it took me way too much time to figure out what was going on: the key passed has been invalidated by the setCacheLimit(0). Now that we QVERIFY that the replace() _fails_, it's much easier to backtrack and figure out why it does so and why, consequently, the following find() is also expected to fail. As a drive-by, reorder two lines so the grouping becomes clearer (blocks now both headed by setCacheLimit()). Pick-to: 6.6 6.5 6.2 5.15 Change-Id: I434b65fc13c3fed6512036efeb98d738eeb2a13d Reviewed-by: Volker Hilsheimer <volker.hilsheimer@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.