qt5base-lts

History

Thiago Macieira 5d48143ff8 Autotest: use QUdpSocket instead of QTcpSocket in tst_QNetworkInterface We don't need to bother the network test server with a TCP SYN packet. All we need is for the local operating system to figure out the IP address it would use to send a packet to the test server. We can do that with QUdpSocket. Also, the network test server hasn't been called "fluke.troll.no" for almost a decade. Change-Id: I209fcd5dbc2b4e5381cffffd14df65ccc7133247 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io>		2017-09-14 13:17:02 +00:00
..
auto	Autotest: use QUdpSocket instead of QTcpSocket in tst_QNetworkInterface	2017-09-14 13:17:02 +00:00
baselineserver	Allow QImage with more than 2GByte of image data	2017-07-08 08:17:13 +00:00
benchmarks	Merge remote-tracking branch 'origin/5.9' into dev	2017-08-31 14:31:31 +02:00
global
manual	Merge dev into 5.10	2017-09-02 10:27:09 +02:00
shared	Fix largefile tests on ARM and QEMU targets	2017-03-28 06:55:32 +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.