Files
harfbuzz/test/shape
Behdad EsfahbodandClaude Opus 4.8 820032a852 [test] Move the USE_MY_METRICS advance regression to an ot-funcs metrics test
The ANT-2026-DQGMHCLX regression was added as a line in
test/shape/data/in-house/tests/variations.tests, but that suite is also
run with --font-funcs=fontations appended by the test runner (which a
.tests line cannot override).  Under fontations funcs this multi-
USE_MY_METRICS composite font's advances differ from HarfBuzz's own, so
the line failed CI.  The divergence is a real HarfBuzz-vs-fontations
difference in how multiple USE_MY_METRICS components are resolved, not a
HarfBuzz bug: HarfBuzz takes the metrics of the last such component.

Remove the .tests line and pin the same regression in
test/api/test-ot-metrics-tt-var.c instead, using hb_font_get_glyph_h_advance,
so it exercises HarfBuzz's own glyph metrics and the fontations CI run does
not touch it.  The font moves to test/api/fonts/ where that test loads it.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-10-31 22:00:12 -06:00
..
2021-08-11 18:49:59 -06:00
2021-08-11 18:49:59 -06:00
2025-06-14 11:02:37 -06:00

Adding tests

You can test shaping of a unicode sequence against a font like this:

$ ./hb-unicode-encode 41 42 43 627 | ../../util/hb-shape font.ttf

assuming an in-tree build. The 41 42 43 627 here is a sequence of Unicode codepoints: U+0041,0042,0043,0627. When you are happy with the shape results, you can use the record-test.sh script to add this to the test suite. record-test.sh requires pyftsubset to be installed. You can get pyftsubset by installing FontTools from https://github.com/behdad/fonttools.

To use record-test.sh, just put it right before the hb-shape invocation:

$ ./hb-unicode-encode 41 42 43 627 | ./record-test.sh ../../util/hb-shape font.ttf

hb-subset and hb-view are resolved as sibling executables next to the provided hb-shape binary.

what this does is:

  • Subset the font for the sequence of Unicode characters requested,
  • Compare the hb-shape output of the original font versus the subset font for the input sequence,
  • If the outputs differ, perhaps it is because the font does not have glyph names; it then compares the output of hb-view for both fonts.
  • If the outputs differ, recording fails. Otherwise, it will move the subset font file into data/in-house/fonts and name it after its hash, and print out the test case input, which you can then redirect to an existing or new test file in data/in-house/tests using -o, e.g.:
$ ./hb-unicode-encode 41 42 43 627 | ./record-test.sh -o data/in-house/tests/test-name.tests ../../util/hb-shape font.ttf

If you created a new test file, add it to data/in-house/meson.build so it is run. Check that make check does indeed run it, and that the test passes. When everything looks good, git add the new font as well as the new test file if you created any. You can see what new files are there by running git status data/in-house. And commit!

Note! Please only add tests using Open Source fonts, preferably under OFL or similar license.