|
|
              
Acceptance tests for Qt3DAs described in the Introduction Qt3D is the C++ framework that underlies Qt3D. This section of the documentation contains some recommended acceptance tests for use when verifying that Qt3D has been successfully ported to a new platform or device, and to determine if the major features of Qt3D work correctly prior to a release. The list of tests is not intended to be exhaustive. When reporting bugs, please include as much information as possible about your platform and particularly its OpenGL implementation. The qglinfo program in the Qt3D source tree can be used to collect up information about the OpenGL version, features, and extensions. On X11 systems, usually glxinfo can be run to obtain similar information. Packaging VerificationWhere Qt Quick 3D has been packaged into a new packaging format, follow these steps to confirm that the newly installed package has validly set up a correct Qt Quick 3D environment. 1) Launch Qt Creator 2) Choose "File" > "New File or Project..." 3) Choose "Qt Quick Project" > "Qt Quick UI", press "Choose..." 4) Name the project "acceptance" and leave the default location 5) A template with QML code is generated. Edit the code so that it appears as follows: import QtQuick 2.0 import Qt3D 1.0 Viewport { width: 400; height: 400 } 6) Choose "File" > "Save" 7) Select the "Projects" tab, and set the "Qt Version:" to be the path of the qmake binary for the Qt where the newly installed Qt Quick 3D is located. Use the "Manage" button to add this Qt to the list if necessary. 8) If the package is correctly installed the code above should be clear of any error-underlining (a red wavy line indicating a problem). 9) Choose "Build" > "Run", ensuring the "acceptance" project is selected. 10) A 400 x 400 black viewport should be displayed. Basic bring-upA pre-requisite for the acceptance tests is that Qt and Qt3D have been built and installed in accordance with the build instructions. In particular, Qt must be configured with OpenGL support and QGLWidget must be working. First, run all unit tests on the platform or device and verify that they all pass (report bugs for those that do not pass). The "make check" rule can be used to run the unit tests if you are not cross-compiling. For cross-compile environments, copy all of the tst_* binaries under tests/auto to the device and run them. Next, run the Teapot Example and verify that it looks similar to the following picture:
Verify that there is no horizontal or vertical distortion, as shown in the following pictures:
Resize the window if possible. The teapot should change scale but keep its relative horizontal and vertical size without distortion. Next, verify that the teapot can be rotated using either the mouse or the cursor keys:
If the teapot does not appear at all, then check stdout for any error and warning messages from the GLSL shader compiler. AnimationsRun the Basket Example and verify that the basket spins on its vertical axis, and continues to do so as the window is resized or the orientiation is changed with the mouse or keyboard. The model should also be textured with a basket weave pattern:
Running the basket example with the environment variable QT3D_LOG_EVENTS set to 1 should produce some qDebug() output that indicates the number of milliseconds per frame, and hence the frame rate: $ QT3D_LOG_EVENTS=1 ./basket ... LOG[0:00:01.681]: ENTER: QGLView::paintGL (16 ms since last enter) LOG[0:00:01.681]: LEAVE: QGLView::paintGL (0 ms elapsed) LOG[0:00:01.696]: ENTER: QGLView::paintGL (15 ms since last enter) LOG[0:00:01.696]: LEAVE: QGLView::paintGL (0 ms elapsed) LOG[0:00:01.713]: ENTER: QGLView::paintGL (17 ms since last enter) ... If the basket does not spin, then try to determine if BasketView::paintGL() is being called every frame or not. If it is being called over and over, then the problem may be in Qt3D. But if it is not being called repeatedly, then it could be a problem in Qt's animation framework or QGLWidget update processing. Rendering into a framebuffer objectRun the Nesting example to test if rendering into a framebuffer object works:
The teapot on the side of the blue cube is the part of the scene that uses a framebuffer object. The teapot should be spinning. This test also checks that alpha blending works in the underlying OpenGL implementation. Model loadingRun the Penguin example to check that 3DS model loading basically works:
If the model fails to appear, it is possible that the 3DS plug-in has not been installed correctly or it could not be located at runtime. It is recommended that you set the QT_DEBUG_PLUGINS environment variable to 1 to get extra information about why the plug-in could not be loaded. Qt3D VerificationRun the Qt3D version of the bouncing Teapot Example using "qmlviewer -opengl teapot-bounce.qml". The teapot should have a shiny appearence (compared to the grey teapot above) and bounce up and down:
It should be possible to rotate the teapot using the mouse and keyboard. Note that when running Qt3D examples on a device that both the QML files and the model files must be copied to the device (the model file is "teapot.bez" in the case of the bouncing teapot example). Object pickingRun the Qt3D Tea Service demo with "qmlviewer -opengl teaservice.qml". Click on the teapot, teacups, and teaspoons to make them jump up, and click on the teapot spout and handle for other effects. This example tests object picking and QML animations.
Note: It may be necessary to adjust the width and height properties in teaservice.qml to match the device's screen size. Build testsThe Qt3D code base contains a number of #ifdef statements that may cause the build to fail in non-default Qt configurations or when strict API options are enabled. It is recommended that these configurations be verified periodically, particularly prior to a release. qmake opengl.pro \ DEFINES+=QT_NO_DEBUG_STREAM \ DEFINES+=QT_NO_DATASTREAM \ DEFINES+=QT_NO_CAST_FROM_BYTEARRAY \ DEFINES+=QT_NO_CAST_TO_ASCII \ DEFINES+=QT_NO_CAST_FROM_ASCII |
