Two examples were given, one to show "invalid" usage that would, in fact, work now - producing a date in 2012 - and the other to show "correct" code which, while correctly delivering the date in 1912 its author appears to have meant (albeit, giving a four-digit year would have made that clearer), uses the string API where code should normally construct dates - much more efficiently - by just passing the numbers to suitable constructors. Add tests verifying that the two date-times from the out-of-date examples do in fact work, even if you tell them the wrong century as default for two-digit dates. Pick-to: 6.7 6.5 Change-Id: I8155af019c80729323ba3958fe3942a72bfefc22 Reviewed-by: Thiago Macieira <thiago.macieira@intel.com> (cherry picked from commit 82d85c16d912b25bfa5b0a081e515fcecda1f975) Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
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.