summaryrefslogtreecommitdiff
path: root/test/bitmap-font.c
AgeCommit message (Collapse)AuthorFilesLines
2008-10-31[test] Build test suite into single binary.Chris Wilson1-15/+7
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-10-18[test/bitmap] Leak on error path.Chris Wilson1-0/+8
Free the FcPattern on error.
2008-09-25Make the bitmap-font an XFAIL.Carl Worth1-1/+2
We've had these PDF and PS failures here for a *long* time, (before the last major release for sure). It's a bug, but we expect it to be there, so advertise it that way.
2008-08-13[test] Preparatory work for running under memfault.Chris Wilson1-13/+10
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-15[test/bitmap-font] Destroy the font options after use.Chris Wilson1-0/+2
Fix the leak of the font options.
2008-01-28Fix bitmap-font test by using near-equality for double comparisonCarl Worth1-5/+6
2008-01-25[test/bitmap-font] Test under all combinations of hinting, test font metrics tooBehdad Esfahbod1-8/+94
This is now failing as we compute NAN font metrics for bitmap-only fonts under disabled metrics hinting. A very infamous bug excercised with PangoCairo's PDF output.
2007-03-05[test] In the bitmap-font test, break cairo_text_path() call into twoBehdad Esfahbod1-2/+4
such that it checks current-point handling after that call. It fails now, because cairo_text_path does not set current-point explicitly.
2006-09-09test/bitmap-font: Fix arguments to FcFreeTypeQuery to avoid warnings.Carl Worth1-2/+2
2006-08-31[test] Use FcFreeTypeQueryBehdad Esfahbod1-5/+5
2006-08-17bitmap-font: Add cairo_text_path;fill to demonstrate bug #7889Carl Worth1-3/+10
2006-08-17Add rotation to bitmap-font to demonstrate failure of bug #7888Carl Worth1-1/+10
2006-08-08Eliminate most compiler warnings from the test suiteCarl Worth1-1/+1
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-20New bitmap-font test with bundled 6x13 font.Carl Worth1-0/+106
The 6x13 font is a public-domain terminal font from the X distribution.