qt5base-lts

History

Ryan Chu 4552eddabf Extend the default retry times of QtNetworkSettings::verifyConnection Apparently, it is not enough to just retry 10 times (10 seconds) in the CI network. It happens from time to time that a test fails due to server port is unreachable. Especially, the docker containers are running in a virtual machine on Windows and macOS platforms. In such cases, it needs more time to warm up the service depending on the system loading. Change-Id: Ia0234bff2a82988b62f451e20b50671708784008 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@qt.io>		2019-01-23 15:28:33 +00:00
..
auto	Extend the default retry times of QtNetworkSettings::verifyConnection	2019-01-23 15:28:33 +00:00
baselineserver	Fix compilation	2018-12-03 07:53:00 +00:00
benchmarks	Make convert_generic_to_rgb64 more generic	2019-01-08 15:00:06 +00:00
global
manual	Update manual qsslsocket test to use HTTP/2 instead of spdy	2019-01-22 09:45:41 +00:00
shared	tst_qfileinfo: Refactor ntfsJunctionPointsAndSymlinks()	2018-09-30 09:59:09 +00:00
testserver	Fix the timing issue of vsftpd during boot (probably invalid config)	2019-01-16 18:24:01 +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.