qt5base-lts

History

Tor Arne Vestbø ef935f6e37 Plumb public permission APIs to Android backend The lock and unlock of the Android deadlock mutex is now part of the internal implementation instead of limited to the enum based permission API. It is unclear why `8bca441b6f` added the guard only to this API and not to the string based API as well. The check for isBackgroundLocationApi29 has been removed, as the logic seemingly resulted in accepting every single permission type except location permissions if used via the enum-based API. Since Android's platform permission API doesn't have an Undetermined status, we keep a hash of the status for each permission type, and by default checkPermission() would return Undetermined, until a requestPermission() call is done which updates the internal hash, and after that checkPermission() would return properly Granted/Denied. Task-number: QTBUG-100413 Change-Id: Ia95c76af754481a281bc90198e349966c9c2da52 Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>		2022-11-09 14:22:29 +02:00
..
auto	tst_QVariant: convert some test functions to table-driven	2022-11-09 04:05:50 -07:00
baseline	Port from container::count() and length() to size() - V5	2022-11-03 14:59:24 +01:00
benchmarks	Port from container::count() and length() to size() - V5	2022-11-03 14:59:24 +01:00
global
libfuzzer	Change the license of all CMakeLists.txt and *.cmake files to BSD	2022-08-23 23:58:42 +02:00
manual	Plumb public permission APIs to Android backend	2022-11-09 14:22:29 +02:00
shared	Tests: fix namespaced build on Windows	2022-10-25 18:33:14 -07:00
testserver	Use SPDX license identifiers	2022-05-16 16:37:38 +02:00
CMakeLists.txt	Change the license of all CMakeLists.txt and *.cmake files to BSD	2022-08-23 23:58:42 +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.