SkQP stands for SKIA Quality Program conformance tests. Basically, it has sets of rendering tests and unit tests to ensure that SKIA is meeting its design specifications on a specific device.

The rendering tests have support for GL, GLES and Vulkan backends and test some rendering scenarios. And the unit tests check the GPU behavior without rendering images.


Render tests design

It is worth noting that rendertests.txt can bring some detail about each test expectation, so each test can have a max pixel error count, to tell SkQP that it is OK to have at most that number of errors for that test. See also:


Each rendertests.txt and unittest.txt file must be located inside a specific subdirectory inside SkQP assets directory.

Test type


Render tests


Unit tests


The script will make the necessary modifications to separate rendertests.txt for each backend-driver combination. As long as the test files are located in the expected place:

Test type


Render tests


Unit tests


Where SKQP_BACKEND can be:

  • gl: for GL backend

  • gles: for GLES backend

  • vk: for Vulkan backend

Example file

  • GPU_DRIVER: freedreno

  • GPU_VERSION: freedreno-a630


SkQP reports

SkQP generates reports after finishing its execution, they are located at the job artifacts results directory and are divided in subdirectories by rendering tests backends and unit tests. The job log has links to every generated report in order to facilitate the SkQP debugging.

Maintaining SkQP on Mesa CI

SkQP is built alongside with another binary, namely list_gpu_unit_tests, it is located in the same folder where skqp binary is.

This binary will generate the expected unittests.txt for the target GPU, so ideally it should be executed on every SkQP update and when a new device receives SkQP CI jobs.

  1. Generate target unit tests for the current GPU with ./list_gpu_unit_tests > unittests.txt

  2. Run SkQP job

  3. If there is a failing or crashing unit test, remove it from the corresponding unittests.txt

  4. If there is a crashing render test, remove it from the corresponding rendertests.txt

  5. If there is a failing render test, visually inspect the result from the HTML report
    • If the render result is OK, update the max error count for that test

    • Otherwise, or put -1 in the same threshold, as seen in SkQP reports

  6. Remember to put the new tests files to the locations cited in Location