summaryrefslogtreecommitdiff
path: root/tests/markup-parse.c
Commit message (Collapse)AuthorAgeFilesLines
* tests: Use the appropriate GTest APIEmmanuele Bassi2020-04-141-7/+3
| | | | | | | | Do not use homegrown assertion and failure macros, when GTest has perfectly functional API to deal with all the cases Pango covers. Using GTest also allows us to rely on appropriate formatting for results and logging.
* markup-parse: don't duplicate codeRoss Burton2019-03-251-150/+3
| | | | Use the functions in test-common.c instead of replicating them.
* tests/markup-parse.c: Fix build on Visual StudioChun-wei Fan2018-03-301-1/+7
| | | | | Visual Studio does not ship with a unistd.h, so include the proper header on Windows when unistd.h is not found on Windows.
* Test attribute iteratorsMatthias Clasen2018-01-031-4/+64
| | | | | | Add a quick test for iterating through attribute lists that piggy-backs on the markup tests - we already have attribute lists and a place for expected results here.
* Add a testcase for font-features in markupMatthias Clasen2015-08-141-0/+3
|
* Add some tests for markup with alphaMatthias Clasen2015-08-141-0/+6
|
* Add tests for pango markupMatthias Clasen2014-08-281-0/+249
This test is modeled after the GMarkup parser tests in GLib. Test file with a name ending in .markup can be dumped in tests/markups/, and tests/markup-parse can be used to generate the expected output files which should be in the same location and with the extension .markup replaced by .expected. The test is also used as an installed test.