qt5base-lts

History

Edward Welbourne b5950f6aff Use QChar::fromUcs4(i) rather than QChar(i) on out-of-range i Follow-up to commit `915be6606e`, catching some benchmarks that took for granted they can assign an arbitrary int to QChar. Since 6.0 this has triggered an assertion. Given the choice between limiting the range (from 100000 to 0x10000) and actually handling the out-of-range values as UCS-4 data, the latter seemed like a more interesting test. At the same time, take the construction of the strings out of the loop, as that's not a QMap performance matter, it's a QString one. Pick-to: 6.1 6.2 Task-number: QTBUG-91713 Change-Id: Id6abab08b5c879f0f764350f66d6aa1dd9f1620a Reviewed-by: Andrei Golubev <andrei.golubev@qt.io> Reviewed-by: Giuseppe D'Angelo <giuseppe.dangelo@kdab.com>		2021-07-22 18:49:16 +02:00
..
auto	Sync default action when checking tool button programmatically	2021-07-22 16:17:49 +02:00
baselineserver	Another round of replacing 0 with nullptr	2020-10-07 23:02:47 +02:00
benchmarks	Use QChar::fromUcs4(i) rather than QChar(i) on out-of-range i	2021-07-22 18:49:16 +02:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
libfuzzer	fuzzing: Add instructions how to reproduce issues from oss-fuzz	2021-06-16 22:53:36 +00:00
manual	QNetworkInformation: Give the manual test a GUI	2021-07-13 16:37:19 +02:00
shared	Refactor createSymbolicLink() and createNtfsJunction()	2021-06-02 23:02:45 +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	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00

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.