king
/
v811_spc009
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '8f4c154c05'
${ noResults }
v811_spc009/external/angle/doc/dEQP.md

4.4 KiB
Raw Blame History

ANGLE + dEQP

drawElements (dEQP) is a very robust and comprehensive set of open-source tests for GLES2, GLES3+ and EGL. They provide a huge net of coverage for almost every GL API feature. ANGLE by default builds dEQP testing targets for testing against GLES 2, GLES 3, EGL, and GLES 3.1 (on supported platforms).

How to build dEQP

You should have dEQP as a target if you followed the DevSetup instructions. Current targets:

  • angle_deqp_gles2_tests for GLES 2.0 tests
  • angle_deqp_gles2_no_gtest for GLES 2.0 tests without google test suite
  • angle_deqp_gles3_tests for GLES 3.0 tests
  • angle_deqp_gles3_no_gtest for GLES 3.0 tests without google test suite
  • angle_deqp_egl_tests for EGL 1.x tests
  • angle_deqp_egl_no_gtest for EGL 1.x tests without google test suite
  • angle_deqp_gles31_tests for GLES 3.1 tests (currently very experimental)
  • angle_deqp_gles31_no_gtest for GLES 3.1 tests (currently very experimental) without google test suite

How to use dEQP

Note: To run an individual test, use the --deqp-case flag on any of the no_gtest targets. It supports simple wildcard support. For example: --deqp-case=dEQP- GLES2.functional.shaders.linkage.*. The gtest targets support wildcards via the --gtest_filter argument, but have different test names.

The tests lists are sourced from the Android CTS masters in third_party/VK-GL-CTS/src/android/cts/master. See gles2-master.txt, gles3-master.txt, gles31-master.txt and egl-master.txt.

If you're running a full test suite, it might take very long time. Running in Debug is only useful to isolate and fix particular failures, Release will give a better sense of total passing rate.

Choosing a Renderer

By default ANGLE tests with D3D11 on Windows, GLES on mobile and Desktop GL otherwise. To specify the exact platform for ANGLE + dEQP, use the arguments:

  • --deqp-egl-display-type=angle-d3d11 for D3D11 (highest available feature level)
  • --deqp-egl-display-type=angle-d3d9 for D3D9
  • --deqp-egl-display-type=angle-d3d11-fl93 for D3D11 Feature level 9_3
  • --deqp-egl-display-type=angle-gl for OpenGL Desktop (OSX, Linux and Windows)
  • --deqp-egl-display-type=angle-gles for OpenGL ES (Android/ChromeOS, some Windows platforms)
  • --deqp-egl-display-type=angle-metal for Metal (Mac)
  • --deqp-egl-display-type=angle-swiftshader for Vulkan with SwiftShader as driver (Android, Linux, Mac, Windows)
  • --deqp-egl-display-type=angle-vulkan for Vulkan (Android, Linux, Windows)

The flag --use-angle=X has the same effect as --deqp-egl-display-type=angle-X.

Check your results

If run from Visual Studio 2015, dEQP generates a test log to out/sln/obj/src/tests/TestResults.qpa. To view the test log information, you'll need to use the open-source GUI Cherry. ANGLE checks out a copy of Cherry to angle/third_party/cherry when you sync with gclient. Note, if you are using ninja or another build system, the qpa file will be located in your working directory.

See the official Cherry README for instructions on how to run Cherry on Linux or Windows.

GoogleTest, ANGLE and dEQP

ANGLE also supports the same set of targets built with GoogleTest, for running on the bots. We don't currently recommend using these for local debugging, but we do maintain lists of test expectations in src/tests/deqp_support. When you fix tests, please remove the suppression(s) from the relevant files!

Running dEQP on Android

Running the tests not using the test runner is tricky, but is necessary in order to get a complete TestResults.qpa from the dEQP tests (since the runner shards the tests, only the results of the last shard will be available when using the test runner). First, use the runner to install the APK, test data and test expectations on the device. After the tests start running, the test runner can be stopped with Ctrl+C. Then, run

adb shell am start -a android.intent.action.MAIN -n org.chromium.native_test/.NativeUnitTestNativeActivity -e org.chromium.native_test.NativeTest.StdoutFile /sdcard/chromium_tests_root/out.txt

After the tests finish, get the results with

adb pull /sdcard/chromium_tests_root/third_party/angle/third_party/deqp/src/data/TestResults.qpa .

Note: this location might change, one can double-check with adb logcat -d | grep qpa.