summaryrefslogtreecommitdiff
path: root/test/linear-gradient.c
AgeCommit message (Collapse)AuthorFilesLines
2008-10-31[test] Build test suite into single binary.Chris Wilson1-14/+6
Avoid calling libtool to link every single test case, by building just one binary from all the sources. This binary is then given the task of choosing tests to run (based on user selection and individual test requirement), forking each test into its own process and accumulating the results.
2008-08-13[test] Preparatory work for running under memfault.Chris Wilson1-2/+2
In order to run under memfault, the framework is first extended to handle running concurrent tests - i.e. multi-threading. (Not that this is a requirement for memfault, instead it shares a common goal of storing per-test data). To that end all the global data is moved into a per-test context and the targets are adjusted to avoid overlap on shared, global resources (such as output files and frame buffers). In order to preserve the simplicity of the standard draw routines, the context is not passed explicitly as a parameter to the routines, but is instead attached to the cairo_t via the user_data. For the masochist, to enable the tests to be run across multiple threads simply set the environment variable CAIRO_TEST_NUM_THREADS to the desired number. In the long run, we can hope the need for memfault (runtime testing of error paths) will be mitigated by static analysis. A promising candidate for this task would appear to be http://hal.cs.berkeley.edu/cil/.
2008-02-20Re-enable pdf tests with gradients and add poppler-based reference imagesCarl Worth1-2/+1
This freezes the current (buggy) poppler result in the test suite so that we will notice any future regressions.
2007-04-27Don't test PDF tests known to fail due to poppler limitationsCarl Worth1-1/+2
The following four tests are disabled: gradient-alpha, linear-gradient, text-pattern, trap-clip We don't use XFAIL as that would disable all backends, (but we can still usefully use these tests on backends other than PDF).
2006-07-13Add prototype for draw in each test file and remove it from the header.Behdad Esfahbod1-0/+2
2006-07-11More test suite infrastructure improvements:Behdad Esfahbod1-2/+3
- Remove cairo_test_expect_failure. cairo-test.c now checks env var CAIRO_XFAIL_TESTS to see if the running test is expected to fail. The reason for expected failure is appended to the test description. - Test description is written out. - Failed/crashed tests also write a line out to stderr (in red), so one can now redirect stdout to /dev/null to only see failures. - cairo_test() has been changed to not take the draw function anymore, instead, draw function is now part of the test struct. - "make check" doesn't allow limiting backends to test using env var anymore. To limit backends to test, one should use the TARGETS variable on the make command line. - "make check-valgrind" now writes its log to valgrind-log instead of valgrind.log, to not interfere with test log file processing.
2006-06-06Remove extraneous whitespace from "blank" lines.Carl Worth1-4/+4
This patch was produced with the following (GNU) sed script: sed -i -r -e 's/^[ \t]+$//' run on all *.[ch] files within cairo.
2006-05-03Shrink the size of a couple of tests (and update reference images).Carl Worth1-3/+3
Shrink linear-gradient and text-pattern test outuput. The real motivation for this is to hide an annoying difference in the gradient output that occurs when under the influence of a device offsets. My opinion is that the gradient output should not change due to just an integer offset, but we currently don't have a precise gradient specification, so this minor deviation really isn't relevant. A better fix for this might have been to make the test suite more forgiving of tiny differences, (perhaps on a per-test basis), but another advantage of shrinking these tests is that they now run a lot faster. It is true that these tests now also exercise fewer different output values, but that's not the designed purpose of the tests so I don't feel bad about losing that characteristic.
2005-04-19Add new cairo_paint function.Carl Worth1-2/+1
Add new get_extents function to the surface backend interface. Add function to query current clip_extents. Implement the new get_extents function for each backend. Save the clip extents from set_clip_region and implement _cairo_surface_get_clip_extents. Abstract away the evil XGetGeometry roundtrip in _cairo_xlib_surface_get_size. Rewrite a couple of tests to call cairo_paint.
2005-04-14and delete:Carl Worth1-18/+13
cairo_set_pattern -> cairo_set_source cairo_get_pattern -> cairo_get_source cairo_set_rgb_color -> cairo_set_source_rgb -> cairo_set_source_rgba cairo_set_alpha -> cairo_get_alpha -> Note that we'll likely want to add cairo_set_source_surface. Add _cairo_stock_color helper function. Improve some interfaces: _cairo_color_init _cairo_color_init_rgb _cairo_color_set_rgb -> _cairo_color_init_rgba _cairo_color_set_alpha _cairo_color_multiply_alpha _cairo_color_get_rgb -> _cairo_color_get_rbga _cairo_color_get_rgba_premultiplied Add cairo_stock_t and some helper macros: CAIRO_COLOR_WHITE CAIRO_COLOR_BLACK CAIRO_COLOR_TRANSPARENT Fix cairo_pattern_t by eliminating pattern->alpha. Fix cairo_solid_pattern_t to use cairo_color_t rather than three doubles. Track removal of pattern->alpha, simplifying the code considerably Track _cairo_color interface changes. Remove gstate->alpha. Propagate down set_source renamings. cairo_pattern_add_color_stop -> cairo_pattern_add_color_stop_rgba and add: cairo_pattern_add_color_stop_rgb Remove pattern->alpha, simplifying the code considerably. Track pattern and color interface changes. Add const where appropriate on cairo_color_t*. Add private type inspection predicate. (cairo_xlib_surface_set_size): Add check for surface type mismatch, (no useful error reporting yet, though). Note coverage as en expected failure. Improve line wrap on expected failure messages. Port all tests to new cairo_set_source interfaces.
2005-03-29More _/- renames in the test directory.Carl Worth1-2/+2
2005-03-09Change the draw function under test to return a cairo_test_status_t so that ↵Carl Worth1-1/+3
it can indicate test failure even if there is no result image.
2005-03-06Comment and clean up the gradient computation. ↵Owen Taylor1-0/+141
(_cairo_linear_pattern_classify): Determine if a linear gradient is horizontal or vertical. (_cairo_pattern_acquire_surface_for_gradient): Optimize horizontal/vertical gradients with a repeating surface. Test case for linear gradients at angles and with a rotated pattern matrix.