qt6-bb10/tests
Łukasz Matysiak 8fd1bbd2db Blacklist tests requiring parsing text > 255 chars on VxWorks
The "many-0 max dec" tests check if a large number (512) of leading zeros
interferes with parsing the number.

The std::from_chars implementation available on VxWorks cannot handle
strings longer than 255 characters.
The number is properly parsed, but the ptr returned as a part of the
std::from_chars_result does not contain the correct result.
It should point to the end of the string (as there is nothing left after the
number), but it wraps and starts to point to other places.
This leads to a wrong value returned by qstrnto(u)ll and to a failing
test.

The issue has been acknowledged by WindRiver. For now, blacklist the
"many-0 max dec" tests.

Pick-to: 6.7
Task-number: QTBUG-115777
Change-Id: I0a897728c71503e6817c69f8ced8ebb0a45295af
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
(cherry picked from commit aea27282b783059ef52e928e811029cedb98ebf9)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
2024-06-26 22:52:30 +00:00
..
auto Blacklist tests requiring parsing text > 255 chars on VxWorks 2024-06-26 22:52:30 +00:00
baseline Skip rendering border for the decoration area of the tree view 2024-06-21 13:34:45 +00:00
benchmarks Add copyright and licensing to build system files missing it 2024-05-21 17:23:21 +02:00
global
libfuzzer Complete color space toICC write 2024-05-31 16:24:50 +02:00
manual AssetDownloader: Add manual test 2024-06-14 13:44:17 +00:00
shared Replace incorrect Metal config check in nativewindow.h 2024-05-01 14:24:06 +02:00
testserver Move shbang lines to before copyright headers 2024-05-23 23:58:10 +02:00
CMakeLists.txt Rid of 'special case' markers 2023-04-13 18:30:58 +02:00
README

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.