6e5c6ef739
Change test data to compile with NO_CAST_FROM_ASCII uncoditionally where casting from ASCII isn't what's being tested by a unittest. The goal is to add a variant of tst_qstring that is compiled with QT_NO_CAST_FROM_ASCII so that the unittests cover that code path too. The commits are split into smaller chunks (where there is a common link between changed code, that code is put in a commit, otherwise I kept the number of changed lines below ~150) to make reviewing them easier. Pick-to: 6.5 Change-Id: I14256f1bde7749a3023753dbb7ed8be72cb6bc14 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.