summaryrefslogtreecommitdiff
path: root/test/huge-radial.c
Commit message (Collapse)AuthorAgeFilesLines
* test: Huge means more than MAX_INTAndrea Canciani2011-01-021-1/+1
| | | | | | | | | Cairo makes it possible to create gradients whose extreme objects are defined with double precision coordinates, but it internally represents them with 24.8 fixed point precision. This shows that coordinates that don't fit the valid range are mishandled and don't even trigger an error status.
* test: Make huge-* test gradients not within pixed_fixed_t rangeAndrea Canciani2011-01-021-1/+1
| | | | | | | | Cairo represents gradients coordinate with 24.8 fixed point precision, but pixman uses 16.16 fixed point coordinates. This shows that cairo is currently unable to handle gradients with coordinates which are valid for cairo but not for pixman.
* [test] Track XFAIL using expected results stored as xfail.pngChris Wilson2009-07-131-1/+1
| | | | | | | | | | | | | | | | Instead of tagging the sources, which is insensitive to changes, track the known failure modes by recording the current fail as an xfail.png reference. (We also introduce a new.png to track a fresh error, so that they are not lost in the noise of the old XFAILs and hopefully do not cause everyone to fret). As we have removed the XFAIL tagging we find, surprise surprise, that some tests are now working -- so review all the reference images (as also some .ref.png now should be .xfail.png). Note: I've only checked image,pdf,ps,svg. The test surfaces report some failures that probably need to addressed in source. I've not correct the changes for win32 and quartz. Nor fixed up the experimental backends.
* [test] Add a huge-radial test case.Chris Wilson2009-01-141-0/+69
Also test the handling of radial gradients with large radii.