AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
0107b695f0
qt5base-lts/tests
History
Ryan Chu 0107b695f0 Make sure docker machine is both created and running before test 
Before reading the configuration of a docker machine, the machine shall
be created and started. Otherwise, the docker command will complain
about "cannot connect to the Docker daemon".

If the docker machine has not been created, the make check will be
immediately terminated, and then print the error message. If its status
is not running, the machine will be turned on by a start command.

Change-Id: I7f4c322e7bdf29e4e4203e0e1bbc2e5c8cf677be
Reviewed-by: Jędrzej Nowacki <jedrzej.nowacki@qt.io>
2018-10-23 05:26:31 +00:00
..
auto Make sure docker machine is both created and running before test 2018-10-23 05:26:31 +00:00
baselineserver Add option to override comparison fuzziness level to lancelot tests 2018-05-03 06:37:16 +00:00
benchmarks tst_qfileinfo: Refactor ntfsJunctionPointsAndSymlinks() 2018-09-30 09:59:09 +00:00
global tst_bic: Add linux-gcc-ia32 bic data for QtXml 2013-01-16 08:25:28 +01:00
manual New proxy model: QConcatenateTablesProxyModel 2018-09-09 10:13:06 +00:00
shared tst_qfileinfo: Refactor ntfsJunctionPointsAndSymlinks() 2018-09-30 09:59:09 +00:00
testserver Docker-based test servers for network-related Qt autotests on macOS 2018-10-18 19:22:46 +00: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.