qt5base-lts

History

Lars Knoll 6abdbb65e5 Change QString::fromLatin1 and friends to use QByteArrayView Also adjust the QString constructor from QByteArray to ignore \0 characters in the string (and not terminate conversion there). [ChangeLog][QtCore][QString] Constructing a QString from a QByteArray will not stop at intermediate '\0' (null) characters in the string as in Qt 5, but will convert all characters in the byte array. Change-Id: I1f6bfefe76dfa9072b165903fec7aa4af1abd882 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2020-10-05 10:12:04 +02:00
..
auto	Change QString::fromLatin1 and friends to use QByteArrayView	2020-10-05 10:12:04 +02:00
baselineserver	Use QList instead of QVector in benchmarks tests	2020-06-25 10:13:31 +02:00
benchmarks	CMake: Regenerate projects to use new qt_internal_ API	2020-09-23 16:59:06 +02:00
global	tst_bic: Add linux-gcc-ia32 bic data for QtXml	2013-01-16 08:25:28 +01:00
libfuzzer	CMake: Regenerate projects to use new qt_internal_ API	2020-09-23 16:59:06 +02:00
manual	Fix rhi manual test build	2020-09-30 17:08:01 +02:00
shared	Replace Q_DECL_UNUSED with [[maybe_unused]]	2020-10-03 11:58:08 +02:00
testserver	Fix perl script warning	2020-03-19 14:15:04 +00:00
.prev_CMakeLists.txt	Make standalone tests build via top level repo project	2019-11-08 15:42:32 +00:00
CMakeLists.txt	CMake: Properly handle CONFIG += thread aka Threads::Threads	2020-08-06 19:15:39 +02:00
README	Doc: Fix references to Qt Test	2013-01-30 01:35:06 +01:00
tests.pro	Build examples and tests only if their requirements are met	2017-03-22 15:55:55 +00: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.