summaryrefslogtreecommitdiff
path: root/test/clip-zero.c
Commit message (Collapse)AuthorAgeFilesLines
* test: Always use DejaVu Sans as default fontAndrea Canciani2015-07-271-1/+1
| | | | | | | | | | This makes the results of the test suite more stable across different environments, because it does not rely anymore on CAIRO_FONT_FAMILY_DEFAULT (which on Windows is "Arial", on Mac "Helvetica"). This change should not affect Linux environments, assuming that the default font is already set to "DejaVu Sans".
* [test] Build test suite into single binary.Chris Wilson2008-10-311-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.
* [test] Preparatory work for running under memfault.Chris Wilson2008-08-131-1/+1
| | | | | | | | | | | | | | | | | | | | 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/.
* [test/*] Create new surfaces using the group target.Chris Wilson2007-12-201-1/+1
| | | | | | | | | | cairo_get_target() returns the original surface passed to cairo_create(), and not the current destination as required when testing drawing to the same surface using multiple contexts. For completeness we also use the group target when creating similar surfaces within the tests (to check that similar surfaces of similar surfaces also work).
* [quartz] Handle creating 0x0 surfacesVladimir Vukicevic2007-12-041-0/+80
Make all 0x0 surfaces be no-ops when used in a rendering operation.