qt5base-lts

History

Edward Welbourne dd5e7f1a52 Use a more robust test for absolute paths in QDir Its filePath() and absoluteFilePath() don't trust its own isAbsolute(), due to some infelicities on MS-Win; and kludged round a consequent problem with resource paths; but other virtual file systems weren't catered for. Replace the convoluted test there with a static bool function (so that future kludges in this area shall only need to edit one place; and can document why they're needed) and use a more robust test that handles all virtual file systems (by asking QFileInfo) but falls back to QFileSystemEntry to work round the known infelicities on MS-Win. Add regression test for asset library paths issue on iOS. Ammends `27f1f84c1c`. Moved a couple of local variables to after the early return, since it doesn't need them, in the process. Task-number: QTBUG-70237 Change-Id: Ib3954826df40ccf816beebe5c3751497e3bf6433 Reviewed-by: Edward Welbourne <edward.welbourne@qt.io> Reviewed-by: Andy Shaw <andy.shaw@qt.io>		2019-01-13 18:18:10 +00:00
..
auto	Use a more robust test for absolute paths in QDir	2019-01-13 18:18:10 +00:00
baselineserver	Fix compilation	2018-12-03 07:53:00 +00:00
benchmarks	Implement support for 16bpc image formats	2018-08-11 14:12:48 +00:00
global
manual	macOS: Only do gamma-corrected blending for subpixel-antialiased text	2018-12-23 12:00:07 +00:00
shared	tests: Include QFileInfo in emulationdetector.h	2018-05-14 12:36:28 +00:00
testserver	Rework QNetworkReply tests to use docker-based test servers	2018-07-27 17:40:27 +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.