mirror of
https://gitlab.freedesktop.org/cairo/cairo.git
synced 2025-12-29 12:40:14 +01:00
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/.
35 lines
775 B
C
35 lines
775 B
C
#include "cairo-test.h"
|
|
|
|
const char png_filename[] = "romedalen.png";
|
|
|
|
static cairo_test_draw_function_t draw;
|
|
|
|
static const cairo_test_t test = {
|
|
"extend-repeat",
|
|
"Test CAIRO_EXTEND_REPEAT for surface patterns",
|
|
256 + 32*2, 192 + 32*2,
|
|
draw
|
|
};
|
|
|
|
static cairo_test_status_t
|
|
draw (cairo_t *cr, int width, int height)
|
|
{
|
|
const cairo_test_context_t *ctx = cairo_test_get_context (cr);
|
|
cairo_surface_t *surface;
|
|
|
|
surface = cairo_test_create_surface_from_png (ctx, png_filename);
|
|
cairo_set_source_surface (cr, surface, 32, 32);
|
|
cairo_pattern_set_extend (cairo_get_source (cr), CAIRO_EXTEND_REPEAT);
|
|
|
|
cairo_paint (cr);
|
|
|
|
cairo_surface_destroy (surface);
|
|
|
|
return CAIRO_TEST_SUCCESS;
|
|
}
|
|
|
|
int
|
|
main (void)
|
|
{
|
|
return cairo_test (&test);
|
|
}
|