fdo-mirrors/cairo
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/cairo/cairo.git synced 2025-12-20 11:40:17 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions
cairo/test/extend-repeat-similar.c

60 lines
1.6 KiB
C
Raw Normal View History

[test/extend-*] Add various cairo_pattern_set_extend() test cases. Add various test cases to exercise _cairo_pattern_acquire_surface_for_surface(), most notably using similar source surfaces to provide coverage of the non-image surface branch.
2008-01-17 17:44:57 +00:00
#include "cairo-test.h"
const char png_filename[] = "romedalen.png";
static cairo_test_draw_function_t draw;
[test] Preparatory work for running under memfault. 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-08-11 21:12:45 +01:00
static const cairo_test_t test = {
[test/extend-*] Add various cairo_pattern_set_extend() test cases. Add various test cases to exercise _cairo_pattern_acquire_surface_for_surface(), most notably using similar source surfaces to provide coverage of the non-image surface branch.
2008-01-17 17:44:57 +00:00
"extend-repeat-similar",
"Test CAIRO_EXTEND_REPEAT for surface patterns",
256 + 32*2, 192 + 32*2,
draw
};
static cairo_surface_t *
clone_similar_surface (cairo_surface_t * target, cairo_surface_t *surface)
{
cairo_t *cr;
cairo_surface_t *similar;
similar = cairo_surface_create_similar (target,
cairo_surface_get_content (surface),
cairo_image_surface_get_width (surface),
cairo_image_surface_get_height (surface));
cr = cairo_create (similar);
[test] Preparatory work for running under memfault. 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-08-11 21:12:45 +01:00
cairo_surface_destroy (similar);
[test/extend-*] Add various cairo_pattern_set_extend() test cases. Add various test cases to exercise _cairo_pattern_acquire_surface_for_surface(), most notably using similar source surfaces to provide coverage of the non-image surface branch.
2008-01-17 17:44:57 +00:00
cairo_set_source_surface (cr, surface, 0, 0);
cairo_set_operator (cr, CAIRO_OPERATOR_SOURCE);
cairo_paint (cr);
[test] Preparatory work for running under memfault. 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-08-11 21:12:45 +01:00
similar = cairo_surface_reference (cairo_get_target (cr));
[test/extend-*] Add various cairo_pattern_set_extend() test cases. Add various test cases to exercise _cairo_pattern_acquire_surface_for_surface(), most notably using similar source surfaces to provide coverage of the non-image surface branch.
2008-01-17 17:44:57 +00:00
cairo_destroy (cr);
return similar;
}
static cairo_test_status_t
draw (cairo_t *cr, int width, int height)
{
[test] Preparatory work for running under memfault. 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-08-11 21:12:45 +01:00
const cairo_test_context_t *ctx = cairo_test_get_context (cr);
[test/extend-*] Add various cairo_pattern_set_extend() test cases. Add various test cases to exercise _cairo_pattern_acquire_surface_for_surface(), most notably using similar source surfaces to provide coverage of the non-image surface branch.
2008-01-17 17:44:57 +00:00
cairo_surface_t *surface;
cairo_surface_t *similar;
[test] Preparatory work for running under memfault. 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-08-11 21:12:45 +01:00
surface = cairo_test_create_surface_from_png (ctx, png_filename);
[test/extend-*] Add various cairo_pattern_set_extend() test cases. Add various test cases to exercise _cairo_pattern_acquire_surface_for_surface(), most notably using similar source surfaces to provide coverage of the non-image surface branch.
2008-01-17 17:44:57 +00:00
similar = clone_similar_surface (cairo_get_group_target (cr), surface);
cairo_set_source_surface (cr, similar, 32, 32);
cairo_pattern_set_extend (cairo_get_source (cr), CAIRO_EXTEND_REPEAT);
cairo_paint (cr);
cairo_surface_destroy (similar);
cairo_surface_destroy (surface);
return CAIRO_TEST_SUCCESS;
}
int
main (void)
{
return cairo_test (&test);
}
Reference in a new issue Copy permalink