qtdeclarative/tests
Alexandru Croitor 4fff2bb14e Fix QQml_setParent_noEvent not to print undefined behavior errors
When building Qt with -fsanitize undefined, the usage of
QQml_setParent_noEvent caused the following error message:
"qqmlglobal_p.h:233:5: runtime error: downcast of address
0x60300061bf10 which does not point to an object of type
'QQmlGraphics_DerivedObject'".

Instead of casting to the referred type, use QObjectPrivate::get to
access the d_ptr.

Change-Id: I2f2224bdb20a8d2e35a3291961378231f03c4ba2
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-12-18 12:02:39 +00:00
..
auto
benchmarks Fix QQml_setParent_noEvent not to print undefined behavior errors 2017-12-18 12:02:39 +00:00
global
manual flingAnimation manual test: add velocity vectors; install a ball return 2017-12-13 06:53:21 +00:00
system
testapplications
README
tests.pro

README

This directory contains autotests and benchmarks based on QTestlib. 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.