qt6-bb10

History

Edward Welbourne 82ad4be4a2 Fix various uncommon cases in QTzTimeZonePrivate backend Includes a fixup for `03fadc26e7`, which removed the check on empty transition list, needed when no data are available. Ensured that such a data-free zone would in fact be noticed as invalid during init(). Fixed handling of times before the epoch (we still want to consult a POSIX rule, if that's all that's available) while ensuring we (as documented) ignore DST for such times. Fixed handling of large times (milliseconds since epoch outside int range) when looking up POSIX rules. Gave QTimeZonePrivate a YearRange enum (to be moved to QTimeZone once this merges up to dev) so as to eliminate a magic number (and avoid adding another). Moved year-munging in POSIX rules after the one early return, which doesn't need the year range. Added test-cases for the distant past/future (just checking UTC's offsets; SLES has a minimal version of the UTC data-file that triggers the bugs fixed here for them). Fixes: QTBUG-74666 Fixes: QTBUG-74550 Change-Id: Ief7b7e55c62cf11064700934f404b2fc283614e1 Reviewed-by: Tony Sarajärvi <tony.sarajarvi@qt.io> Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>		2019-04-05 20:31:26 +00:00
..
auto	Fix various uncommon cases in QTzTimeZonePrivate backend	2019-04-05 20:31:26 +00:00
baselineserver	Do not mix QByteArray with QString in arithmetic	2019-03-08 14:20:54 +00:00
benchmarks	Add cmdline feature to qmake	2019-02-18 07:12:14 +00:00
global	…
manual	Manual dialog test: Output URLs when testing QFileDialog	2019-04-05 05:57:17 +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.