qt5base-lts

History

Lars Knoll ba26496647 Don't crash when calling jumpToFrame() on an empty QMovie Properly return an invalid frame when calling jumpToFrame() with a non existent frame number. Fixes: QTBUG-79029 Change-Id: Ic40f4a6de3106fab42c0bb6c961194be47b04e31 Reviewed-by: Eirik Aavitsland <eirik.aavitsland@qt.io>		2019-10-09 15:58:26 +02:00
..
auto	Don't crash when calling jumpToFrame() on an empty QMovie	2019-10-09 15:58:26 +02:00
baselineserver	Update lancelot tests to use non-system-specific host info collection	2019-09-04 13:09:39 +00:00
benchmarks	Merge remote-tracking branch 'origin/5.12' into 5.13	2019-07-26 10:13:06 +02:00
global
libfuzzer	Fix typos in readme	2019-07-11 14:17:08 +02:00
manual	tests: fix typo in comment	2019-09-23 10:27:56 +02:00
shared	tst_qfileinfo: Refactor ntfsJunctionPointsAndSymlinks()	2018-09-30 09:59:09 +00:00
testserver	Select single-name SSL certificate for test servers using host network	2019-01-28 14:03:34 +00:00
README
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.