You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
33 lines
1.1 KiB
33 lines
1.1 KiB
[]{#Unit_Test}Unit Test[](#Unit_Test){.section_anchor}
|
|
======================================================
|
|
|
|
sfntly C++ port uses Google testing framework for unit testing.
|
|
|
|
All test cases are under src/test.
|
|
|
|
To run the unit test, you need to compile sfntly first, then copy
|
|
Tuffy.ttf from data/ext to the folder that unit\_test(.exe) is located.
|
|
Run the unit\_test.
|
|
|
|
If you are only interested in one test case, for example, you are
|
|
working on name table and only wants name editing test, you can use the
|
|
gtest\_filter flag in command line.
|
|
|
|
``` {.prettyprint}
|
|
unit_test --gtest_filter=NameEditing.*
|
|
```
|
|
|
|
For more info regarding running a subset of gtest, please see [GTest
|
|
Advanced
|
|
Guide](http://code.google.com/p/googletest/wiki/V1_6_AdvancedGuide).
|
|
|
|
Its strongly suggested to run unit\_tests with valgrind. The following
|
|
example shows a typical test command
|
|
|
|
``` {.prettyprint}
|
|
valgrind --leak-check=full -v ./unit_test --gtest_filter=*.*-FontData.*
|
|
```
|
|
|
|
FontData tests are the longest and you may want to bypass them during
|
|
development. They shall be run in bots, however.
|