summaryrefslogtreecommitdiff
path: root/test/README
diff options
context:
space:
mode:
authorBryce W. Harrington <b.harrington@samsung.com>2013-06-20 03:16:01 +0000
committerChris Wilson <chris@chris-wilson.co.uk>2013-06-20 11:00:59 +0100
commitd4545910e2836eb6fc7dc2ed787b02aea514cb0b (patch)
tree49750d403d7a936a8f8f45f48997d6dad7281cd3 /test/README
parent982f288460591a8f2b8a78db89ae6e5495d2b3b8 (diff)
downloadcairo-d4545910e2836eb6fc7dc2ed787b02aea514cb0b.tar.gz
test: Note naming scheme for XFAIL images in README
Signed-off-by: Bryce Harrington <b.harrington@samsung.com>
Diffstat (limited to 'test/README')
-rw-r--r--test/README5
1 files changed, 3 insertions, 2 deletions
diff --git a/test/README b/test/README
index fef240dae..bbb3596a0 100644
--- a/test/README
+++ b/test/README
@@ -256,8 +256,9 @@ correct, then there's likely a bug in poppler. In this case, we can
simply report the poppler bug, (making it block 12143 above), post the
PDF result from the test suite, and list the bug in this file. Once
we've done this, we can capture poppler's buggy output as a
-pdf-specific reference image so that the test suite will regard the
-test as passing, (and we'll ensure there is no regression).
+pdf-specific reference image (as reference/*.xfail.png) so that the
+test suite will regard the test as passing, (and we'll ensure there
+is no regression).
Once the poppler bug gets fixed, the test suite will start reporting a
false negative again, and this will be easy to fix by simply removing