Continuous testing of a terminal font

A description of how and why my 3270 terminal font is tested and how other similar artifacts can be tested.

Transcript

1. Continuous Testing of a Terminal Font
2. Why this font?
5. What is a font after all?
7. If it’s software, how do you test it?
8. How do I test it • The auxiliary programs can be tested with the usual tools we already know • Github, Bitbucket, and Gitlab are easy to integrate with 3rd parties • This is travis.yaml
9. In the Makefile
10. Did you notice? • On the first lines • These are for the simple utilities that build things like grids and sample images
11. Some rough edges • Rendering problems require some degree of visual inspection • Different platforms render differently (Windows, Mac, and Linux, each have their own quirks
13. What else?
14. Google Fonts! • Insanely high bar • Very comprehensive tooling (Font Bakery) tests EVERYTHING • We’re not there yet
15. So? • It’s doable: fonts are software • Ensures a base level of quality – This font is now distributed with Debian and Ubuntu, so it’s no longer just my hobby project – other people use it. • The same machinery you use to test your software can test pretty much anything
16. Demo time!
17. ?
18. If you want to know more (or to get the font): https://github.com/rbanffy/3270font