Running the tests

This page provides instructions for running deqp tests in Linux and Windows environments, using command line arguments, and working with the Android application package.

Linux and Windows environments

Start by copying the following files and directories to the target.

Module Directory Target
Execution Server build/execserver/execserver <dst>/execserver
EGL Module build/modules/egl/deqp-egl <dst>/deqp-egl
GLES2 Module build/modules/gles2/deqp-gles2 <dst>/deqp-gles2
data/gles2 <dst>/gles2
GLES3 Module build/modules/gles3/deqp-gles3 <dst>/deqp-gles3
data/gles3 <dst>/gles3
GLES3.1 Module build/modules/gles31/deqp-gles31 <dst>/deqp-gles31
data/gles31 <dst>/gles31
GLES3.2 Module build/modules/gles32/deqp-gles32 <dst>/deqp-gles32
data/gles32 <dst>/gles32

You can deploy the execution service and test binaries anywhere in the target file system; however, test binaries expect to find data directories in the current working directory. When ready, start the Test Execution Service on the target device. For details on starting the service, see Test execution service.

Command line arguments

The following table lists command line arguments that affect execution of all test programs.

Argument Description
--deqp-case=<casename> Run cases that match a given pattern. Wildcard (*) is supported.
--deqp-log-filename=<filename> Write test results to the file whose name you provide. The test execution service will set the filename when starting a test.
--deqp-stdin-caselist
--deqp-caselist=<caselist>
--deqp-caselist-file=<filename>
Read case list from stdin or from a given argument. The test execution service will set the argument according to the execution request received. See the next section for a description of the case list format.
--deqp-test-iteration-count=<count> Override iteration count for tests that support a variable number of iterations.
--deqp-base-seed=<seed> Base seed for the test cases that use randomization.

GLES2 and GLES3-specific arguments

The following table lists the GLES2- and GLES3-specific arguments.
Argument Description
--deqp-gl-context-type=<type> OpenGL context type. Available context types depend on the platform. On platforms supporting EGL, the value egl can be used to select the EGL context.
--deqp-gl-config-id=<id> Run tests for the provided GL configuration ID. Interpretation is platform-dependent. On the EGL platform, this is the EGL configuration ID.
--deqp-gl-config-name=<name> Run tests for a named GL configuration. Interpretation is platform-dependent. For EGL, the format is rgb(a)<bits>d<bits>s<bits>. For example, a value of rgb888s8 will select the first configuration where the color buffer is RGB888 and the stencil buffer has 8 bits.
--deqp-gl-context-flags=<flags> Creates a context. Specify robust or debug.
--deqp-surface-width=<width>
--deqp-surface-height=<height>
Try to create a surface with a given size. Support for this is optional.
--deqp-surface-type=<type> Use a given surface type as the main test rendering target. Possible types are window, pixmap, pbuffer, and fbo.
--deqp-screen-rotation=<rotation> Screen orientation in increments of 90 degrees for platforms that support it.

Test case list format

The test case list can be given in two formats. The first option is to list the full name of each test on a separate line in a standard ASCII file. As the test sets grow, the repetitive prefixes can be cumbersome. To avoid repeating the prefixes, use a trie (also known as a prefix tree) syntax shown below.

{nodeName{firstChild{…},…lastChild{…}}}

For example:

{dEQP-EGL{config-list,create_context{rgb565_depth_stencil}}}

Translates into the following two test cases:

dEQP-EGL.config_list
dEQP-EGL.create_context.rgb565_depth_stencil

Android

The Android application package contains all required components, including the test execution service, test binaries, and data files. The test activity is a NativeActivity that uses EGL (requires Android 3.2 or higher).

The application package can be installed with the following command (name shown is the name of the APK in the Android CTS package; which name depends on the build):

adb –d install –r com.drawelements.deqp.apk

To launch the test execution service and to setup port forwarding, use the following:

adb –d forward tcp:50016 tcp:50016
adb –d shell am start –n com.drawelements.deqp/.execserver.ServiceStarter

Debug prints can be enabled by executing the following before starting the tests:

adb –d shell setprop log.tag.dEQP DEBUG

Executing tests on Android without Android CTS

To manually start the test execution activity, construct an Android intent that targets android.app.NativeActivity. The activities can be found in the com.drawelements.deqp package. The command line must be supplied as an extra string with key "cmdLine" in the Intent.

A test log is written to /sdcard/dEQP-log.qpa. If the test run does not start normally, additional debug information is available in the device log.

You can launch an activity from the command line using the am utility. For example, to run dEQP-GLES2.info tests on a platform supporting NativeActivity, use the following commands.

adb -d shell am start -n com.drawelements.deqp/android.app.NativeActivity -e \
cmdLine "deqp --deqp-case=dEQP-GLES2.info.* --deqp-log-filename=/sdcard/dEQP-Log.qpa

Debugging on Android

To run the tests under the GDB debugger on Android, first compile and install the debug build by running the following two scripts:

python android/scripts/build.py --native-build-type=Debug
python android/scripts/install.py

After the debug build is installed on the device, to launch the tests under GDB running on the host, run the following command:

python android/scripts/debug.py \
--deqp-commandline="--deqp-log-filename=/sdcard/TestLog.qpa --deqp-case=dEQP-GLES2.functional.*"

The deqp command line depends on the test cases to be executed and other required parameters. The script adds a default breakpoint at the beginning of the deqp execution (tcu::App::App).

The debug.py script accepts multiple command line arguments for actions such as setting breakpoints for debugging, gdbserver connection parameters, and paths to additional binaries to debug (use debug.py --help for all arguments and explanations). The script also copies some default libraries from the target device to get symbol listings.

To step through driver code (such as when the GDB needs to know the locations of the binaries with full debug information), add more libraries via debug.py command line parameters. This script writes out a configuration file for the GDB starting from line 132 of the script file. You can provide additional paths to binaries, etc., but supplying correct command line parameters should be enough.

Note: On Windows, the GDB binary requires libpython2.7.dll. Before launching debug.py, add <path-to-ndk>/prebuilt/windows/bin to the PATH variable.

Note: Native code debugging does not work on stock Android 4.3; for workarounds, refer to this public bug. Android 4.4 and higher do not contain this bug.