qt5base-lts

History

Shawn Rutledge 51a348b2e2 Markdown writer: omit space after opening code block fence The CommonMark spec shows that it's not necessary to have a space between the code fence and the language string: https://spec.commonmark.org/0.29/#example-112 This also avoids a needless trailing space after a code fence that does not include a language string. Change-Id: I2addd38a196045a7442150760b73269bfe4ffb22 Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>		2020-04-20 21:08:32 +02:00
..
auto	Markdown writer: omit space after opening code block fence	2020-04-20 21:08:32 +02:00
baselineserver	Revert "QAbstractSocket: deprecate 'error' member-function"	2020-02-26 23:07:52 +03:00
benchmarks	Replace QTime with QElapsedTimer in benchmarks	2020-04-20 17:44:13 +02:00
global
libfuzzer	Fuzzing: Add fuzz target for QCborStreamReader::next	2020-04-16 21:12:00 +02:00
manual	Fix QTabletEvent manual tests	2020-04-01 22:57:55 +02:00
shared	Fix isRunningArmOnX86 unused function warning	2020-02-03 15:03:51 +01:00
testserver	Fix perl script warning	2020-03-19 14:15:04 +00:00
README
tests.pro

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.