Al b8a12e0517 [test] adding parser test cases in 22 countries. These may change, and I'm generlaly against putting every obscure test case in the world in here. It's better to measure accuracy in aggregate statistics instead of individual test cases (i.e. if a particular change to the parser improves overall performance but fails one test case, should we accept the improvement?) The thought here is: these represent parses that are used in documentation/examples, as well as most of those that have been brought up in Github issues from the initial release, and we want these specific tests to work from build to build. If a model fails one of these test cases, it shouldn't get pushed to our users.

2017-03-20 00:58:52 -04:00

..

greatest.h

[tests] Using greatest (https://github.com/silentbicycle/greatest) for automated testing

2016-01-28 16:31:32 -05:00

Makefile.am

[test] adding the new tests to the Makefile

2017-03-11 14:34:27 -05:00

test_crf_context.c

[fix] don't compare a double to 0

2017-03-15 14:59:33 -04:00

test_expand.c

[test] adding printfs on expansion test failure so it's more clear what's going on

2017-03-17 17:46:22 -04:00

test_numex.c

[fix] vignt => vingt in French numex

2016-03-29 02:18:37 -04:00

test_parser.c

[test] adding parser test cases in 22 countries. These may change, and I'm generlaly against putting every obscure test case in the world in here. It's better to measure accuracy in aggregate statistics instead of individual test cases (i.e. if a particular change to the parser improves overall performance but fails one test case, should we accept the improvement?) The thought here is: these represent parses that are used in documentation/examples, as well as most of those that have been brought up in Github issues from the initial release, and we want these specific tests to work from build to build. If a model fails one of these test cases, it shouldn't get pushed to our users.

2017-03-20 00:58:52 -04:00

test_string_utils.c

[test/utils] also a good thing to sanity check (in C especially): string handling code

2017-03-10 01:15:23 -05:00

test_transliterate.c

[test] adding test of new latin-ascii-simple transliterator which only handles things like HTML entities

2017-03-17 18:27:18 -04:00

test_trie.c

[phrases] Case where trie search finds a match, makes progress beyond the next token but has to fall back. Adding trie search test case

2016-02-08 01:07:56 -05:00

test.c

[test/utils] also a good thing to sanity check (in C especially): string handling code

2017-03-10 01:15:23 -05:00