fonttools/Tests/ttLib/tables/_v_m_t_x_test.py

from fontTools.ttLib.tables._v_m_t_x import table__v_m_t_x
import _h_m_t_x_test
import unittest


class VmtxTableTest(_h_m_t_x_test.HmtxTableTest):
    @classmethod
    def setUpClass(cls):
        cls.tableClass = table__v_m_t_x
        cls.tag = "vmtx"


if __name__ == "__main__":
    import sys

    sys.exit(unittest.main())
[_v_m_t_x_test] add test for vmtx table (simply inherits from hmtx one) 2016-10-14 15:03:21 +01:00			`from fontTools.ttLib.tables._v_m_t_x import table__v_m_t_x`
[Tests] use absolute imports and add __init__.py where relevant We can't use relative imports any more since the tests are now located outside the package. I had to add __init__.py to Tests/feaLib/ so that pytest does not get confused by the presence of two test files with the same basename: i.e. Tests/feaLib/builder_test.py and Tests/feaLib/builder_test.py https://github.com/pytest-dev/pytest/issues/774 http://stackoverflow.com/questions/12582503/py-test-test-discovery-failure-when-tests-in-different-directories-are-called 2017-01-15 21:45:57 +00:00			`import _h_m_t_x_test`
[_v_m_t_x_test] add test for vmtx table (simply inherits from hmtx one) 2016-10-14 15:03:21 +01:00			`import unittest`


			`class VmtxTableTest(_h_m_t_x_test.HmtxTableTest):`
			`@classmethod`
			`def setUpClass(cls):`
			`cls.tableClass = table__v_m_t_x`
			`cls.tag = "vmtx"`


			`if __name__ == "__main__":`
consistently do sys.exit(unittest.main()) in all test modules So that when run as scrips they report test failures with exit code Follow up on b7bb391033ef3255c90134da3d7aef50d2d5326d 2017-01-11 13:05:35 +00:00			`import sys`
Blacken code 2022-12-13 11:26:36 +00:00
consistently do sys.exit(unittest.main()) in all test modules So that when run as scrips they report test failures with exit code Follow up on b7bb391033ef3255c90134da3d7aef50d2d5326d 2017-01-11 13:05:35 +00:00			`sys.exit(unittest.main())`