One of the things that makes Check really useful is that it's very lightweight. However, it engages in a little bit of namespace pollution; instead of prefixing all of its symbols consistently with something like ck_ it sometimes uses prefixes (SRunner), sometimes abbreviations (TCase), and sometimes just the word (Suite).
It would make APIs easier to remember and complete—and make it less likely for Check to step on the toes of code under test—if everything used a consistent naming scheme and prefix. For example, ck_test_case instead of TCase, ck_test_suite instead of Suite, ck_runner instead of SRunner, and so on.
One of the things that makes Check really useful is that it's very lightweight. However, it engages in a little bit of namespace pollution; instead of prefixing all of its symbols consistently with something like
ck_it sometimes uses prefixes (SRunner), sometimes abbreviations (TCase), and sometimes just the word (Suite).It would make APIs easier to remember and complete—and make it less likely for Check to step on the toes of code under test—if everything used a consistent naming scheme and prefix. For example,
ck_test_caseinstead ofTCase,ck_test_suiteinstead ofSuite,ck_runnerinstead ofSRunner, and so on.