qt5base-lts

History

Assam Boudjelthia 45daea19c3 Fix setField JNI template calls The calls were trying to pass a JNIEnv from a QJniEnvironment using conversion operator which was removed, and weren't detected since they are templates and were missing tests. This fix that and add test cases for setField() and setStaticField() calls. Pick-to: 6.1 Change-Id: I6e1e6b7f557bbc664248ad364c48d63f58b70756 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>		2021-05-05 16:28:27 +03:00
..
auto	Fix set*Field JNI template calls	2021-05-05 16:28:27 +03:00
baselineserver	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
benchmarks	Make loop variables references in date benchmark	2021-04-27 15:34:50 +02:00
global
libfuzzer	Fuzzing: Test different calendar systems	2021-04-26 17:51:38 +02:00
manual	Lowercase system includes and lib names for Windows, fix cross compiling	2021-04-23 14:31:04 +03:00
shared	Move QEMU emulation detector to QTest	2021-02-13 10:02:51 +02:00
testserver	Network self-test: make it work with docker/containers	2020-11-17 19:56:06 +01:00
CMakeLists.txt	CMake: Refactor optimization flag handling and add optimize_full	2020-10-06 10:07:05 +02:00
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.