summaryrefslogtreecommitdiff
path: root/test/create-for-stream.c
Commit message (Collapse)AuthorAgeFilesLines
* Fix build on windowsUli Schlachter2021-07-231-0/+5
| | | | Signed-off-by: Uli Schlachter <psychon@znc.in>
* pdf: Properly pass on stdio write errorsUli Schlachter2021-07-231-1/+20
| | | | | | | | | | | | | | | | | | | | cairo-pdf was silently ignoring write errors in _cairo_pdf_surface_finish(). Any write errors that happened here ended up setting a "status" variable, but the value in this variable was then unused. This commit fixes this bug by passing this error on to the caller. Additionally, this also adds a test case for this behaviour based on writing to /dev/full. This file is non-standard and thus the test first checks that this file exists and is writable before trying to write to it. This bug was found based on a report from Knut Petersen [0]. [0]: https://lists.cairographics.org/archives/cairo/2021-July/029281.html Signed-off-by: Uli Schlachter <psychon@znc.in>
* test: Ensure output dirs exist, falling back to current dir if neededBryce W. Harrington2013-09-091-3/+11
| | | | | | | | | | | | | | This change makes several tests behave more like ps-eps.c, et al by making them attempt to mkdir "output", and in case of trouble use "." instead. filenames are now allocated at runtime due to this change, so ensure the corresponding free()'s are in place as well. This should facilitate running the test suite with a relative path outside cairo's source tree, such as when employing the CAIRO_REF_DIR environment variable. Signed-off-by: Bryce Harrington <b.harrington@samsung.com> Signed-off-by: Uli Schlachter <psychon@znc.in>
* test: Fix several tests to place output files in the output directoryBryce W. Harrington2013-09-091-3/+3
| | | | | | | | | | | | | | The standard location for test output is cairo/test/output. The harness itself was updated to write automatically generated images in this directory, however a number of tests generate their own local output files. This patch updates these tests to write their output into CAIRO_TEST_OUTPUT_DIR (which defaults to cairo/test/output) as well, in the interest of decluttering the test directory. Signed-off-by: Bryce Harrington <b.harrington@samsung.com> Signed-off-by: Uli Schlachter <psychon@znc.in>
* [test] Use '.' as the field separator in the namesChris Wilson2008-10-311-1/+1
| | | | | | | | | We frequently use '-' within the test name or format name and so we encounter confusion as '-' is also used as the field separator. At times this has caused a new test to break an old test because the new test would match one of the old test's target specific reference images. So switch everything over to use '.' between fields (test name, target, format, subtest, etc.).
* [test] Build test suite into single binary.Chris Wilson2008-10-311-25/+28
| | | | | | | | | 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] Fix target specific tests for recent SVG/PS version split.Chris Wilson2008-09-271-2/+6
| | | | | | A few tests explicitly checked whether the "ps" or "svg" target was enabled and this broke because of the name change. So fixup, to run the generic test if either PS or SVG target is enabled as appropriate.
* [test] Set CAIRO_TEST_UNTESTED to 77Chris Wilson2008-08-131-1/+10
| | | | | 77 is the magic exit code used by automake to indicate a skipped test, so by using it we can get a slightly more informative test log.
* [test] Export a function to check whether a target is enabled.Chris Wilson2008-08-131-24/+30
| | | | | | Allow individuals tests to check whether a test target is enabled - useful for those tests that circumvent cairo_test() and perform feature testing.
* [test] Preparatory work for running under memfault.Chris Wilson2008-08-131-17/+25
| | | | | | | | | | | | | | | | | | | | 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/.
* Fix create-for-stream test to log its failure properlyCarl Worth2008-01-161-2/+11
| | | | | | Without this, a failure of this test won't be nicely reported in the post-make-check summary. (Also fix a silly little typo in the svg-clip test.)
* [test/create-for-stream] Add the missing cairo_surface_finish().Chris Wilson2007-09-261-0/+1
| | | | | | | | | | | | | Moments after pushing the new test case did I realise the issue... We do not attempt to write out the surface to the user stream until we perform the cairo_surface_destroy() by which point we have lost the ability to interrogate the error status. We can avoid this by explicitly calling cairo_surface_finish() and then checking the error status - and we see that the error is indeed reported correctly. No bug. Nothing to see here. Please move along. (Apart from the request for the status to be return from cairo_surface_destroy!)
* [test/create-for-stream] Add test case for user error propagation.Chris Wilson2007-09-261-13/+44
| | | | | | | | | From bug https://bugs.freedesktop.org/show_bug.cgi?id=7049, we find that the error status from the user supplied write function to cairo_*_surface_create_for_stream is ignored and not propagated back to the surface/context - leading to silent data loss. Incorporate the suggested test case, a write function that simply returns CAIRO_STATUS_WRITE_ERROR, into create-for-stream.c.
* create-for-stream - free resources after test failure.Chris Wilson2007-04-161-17/+20
| | | | | | create-for-stream often fails whilst running under valgrind due to the postscript output containing a CreationDate with seconds resolution, hence the visibility of the resource leaks during failure.
* Augment cairo_test_init with cairo_test_fini to avoid leakCarl Worth2007-03-021-0/+2
| | | | | | Without this, any tests that were using cairo_test_init rather than cairo_test would end up leaking a FILE* for the log file. So this keeps valgrind much more happy with the test suite.
* Eliminate most compiler warnings from the test suiteCarl Worth2006-08-081-1/+3
|
* More test suite infrastructure improvements:Behdad Esfahbod2006-07-111-11/+18
| | | | | | | | | | | | | | | | | - 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.
* Add test case for the PDF, PS and SVG stream constructors.Kristian Høgsberg2006-06-141-0/+218
View Lorry Controller Status