xref: /aosp_15_r20/external/mesa3d/docs/ci/skqp.rst (revision 6104692788411f58d303aa86923a9ff6ecaded22)
1SkQP
2====
3
4`SkQP <https://skia.org/docs/dev/testing/skqp/>`__ stands for SKIA Quality
5Program conformance tests.  Basically, it has sets of rendering tests and unit
6tests to ensure that `SKIA <https://skia.org/>`__ is meeting its design specifications on a specific
7device.
8
9The rendering tests have support for GL, GLES and Vulkan backends and test some
10rendering scenarios.
11And the unit tests check the GPU behavior without rendering images, using any of the GL/GLES or Vulkan drivers.
12
13SkQP reports
14------------
15
16SkQP generates reports after finishing its execution, and deqp-runner collects
17them in the job artifacts results directory under the test name.  Click the
18'Browse' button from a failing job to get to them.
19
20SkQP failing tests
21------------------
22
23SkQP rendering tests will have a range of pixel values allowed for the driver's
24rendering for a given test.  This can make the "expected" image in the result
25output look rather strange, but you should be able to make sense of it knowing
26that.
27
28In SkQP itself, testcases can have increased failing pixel thresholds added to
29them to keep CI green when the rendering is "correct" but out of normal range.
30However, we don't support changing the thresholds in our testing.  Because any
31driver rendering not meeting the normal thresholds will trigger Android CTS
32failures, we treat them as failures and track them as expected failures the
33```*-fails.txt`` file.`
34