Al
|
6d4c7984df
|
[api] doing this now since we're bumping a major version. Using a libpostal prefixes for all public header functions and definitions
|
2017-03-31 03:35:51 -04:00 |
|
Al
|
f7b695c642
|
[build] add /usr/local/include as default include path for test Makefile as well
|
2017-03-30 15:57:17 -04:00 |
|
Al
|
65fadbeea3
|
[fix] add CBLAS_LIBS in the test Makefile
|
2017-03-29 21:38:54 -04:00 |
|
Al
|
9636ef6393
|
[fix] typo
|
2017-03-29 18:55:03 -04:00 |
|
Al
|
0bd1bdb6f2
|
[test] adding Brazil and Romania parses for demo
|
2017-03-29 13:03:05 -04:00 |
|
Al
|
03ceb18a41
|
[test] adding US tests for parser demo queries
|
2017-03-28 15:04:00 -04:00 |
|
Al
|
61d008f349
|
[test] making some of the test cases simpler/easier so they don't fail. In general this should just be for examples that are/are going to be in the docs. Improving overall aggregate statistics like held-out accuracy over time is preferable to worrying about one individual test failure.
|
2017-03-26 20:27:32 -04:00 |
|
Al
|
3aaa628b25
|
[test] add LaSalle, Montréal tests
|
2017-03-21 14:24:13 -04:00 |
|
Al
|
1f1dbe25e1
|
[test] adding a number of user-contributed test cases from Moz in #21. Almost all are working under the CRF parser trained on 10% of the data. There are a few problematic ones in the UK still that have been omitted here. We currently don't correctly format the training data for locailty + postal town pattern, which are both considered "city" by libpostal and thus one will usually get lumped in with the road or something like that. There may also be some utility in modelling comma usage (training data has commas, but they're ignored by the parser both at train and run time - might be useful to train on them but drop out randomly so the parser doesn't become too dependent on having them)
|
2017-03-21 03:08:09 -04:00 |
|
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 |
|
Al
|
8e3c9d0269
|
[test] adding test of new latin-ascii-simple transliterator which only handles things like HTML entities
|
2017-03-17 18:27:18 -04:00 |
|
Al
|
be07bfe35d
|
[test] adding printfs on expansion test failure so it's more clear what's going on
|
2017-03-17 17:46:22 -04:00 |
|
Al
|
f4a9e9d673
|
[fix] don't compare a double to 0
|
2017-03-15 14:59:33 -04:00 |
|
Al
|
7afba832e5
|
[test] adding the new tests to the Makefile
|
2017-03-11 14:34:27 -05:00 |
|
Al
|
dd0bead63a
|
[test/utils] also a good thing to sanity check (in C especially): string handling code
|
2017-03-10 01:15:23 -05:00 |
|
Al
|
adab8ab51a
|
[test/crf] test for crf_context, adapted from crf1dc_debug_context in CRFsuite. Always a good idea to sanity check numerical code
|
2017-03-10 01:13:40 -05:00 |
|
Al
|
3e8ab0ba3f
|
[test] New expansion test with all options set to false
|
2016-07-15 13:26:14 -04:00 |
|
Al
|
879da6214a
|
[test] Adding test for ambiguous expansion
|
2016-04-29 13:27:41 -04:00 |
|
Al
|
378459fde8
|
[fix] vignt => vingt in French numex
|
2016-03-29 02:18:37 -04:00 |
|
Al
|
37cfe8ab3b
|
[test] Adding automated parser tests to the C library
|
2016-02-17 17:19:10 -05:00 |
|
Al
|
cf2a79bef1
|
[api] Default options accessible through getters, not static structs
|
2016-02-15 17:34:00 -05:00 |
|
Al
|
166119f5c3
|
[test] Adding numex tests for the concatenated case
|
2016-02-10 09:26:12 -05:00 |
|
Al
|
ffde22395c
|
[numex] Adding test cases where stopword should not get swallowed into the numeric expression
|
2016-02-10 08:30:53 -05:00 |
|
Al
|
87ef471f8b
|
[test] Adding test cases for tokenized tail search
|
2016-02-08 17:56:28 -05:00 |
|
Al
|
4ed0474f7e
|
[fix] test for normalized output on an expansion with an accented canonical
|
2016-02-08 12:32:14 -05:00 |
|
Al
|
9ac0379a65
|
[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 |
|
Al
|
9b3296914a
|
[build] Defining LIBPOSTAL_DATA_DIR at compile time, not configure
|
2016-01-30 02:18:12 -05:00 |
|
Al
|
0da3774b1e
|
[tests] Relative includes in tests to fix compilation issues on gcc/Ubuntu
|
2016-01-28 17:04:12 -05:00 |
|
Al
|
76445c4bf7
|
[fix] Makefile dir
|
2016-01-28 16:43:17 -05:00 |
|
Al
|
8702ee931c
|
[tests] Main test program and Makefile
|
2016-01-28 16:37:29 -05:00 |
|
Al
|
d318db15f1
|
[tests] Numeric expression parsing tests
|
2016-01-28 16:36:20 -05:00 |
|
Al
|
aa4272ed9e
|
[tests] Transliteration tests
|
2016-01-28 16:36:09 -05:00 |
|
Al
|
f963e175e4
|
[tests] Expansion tests with and without language classifier
|
2016-01-28 16:35:32 -05:00 |
|
Al
|
87899050b2
|
[tests] Using greatest (https://github.com/silentbicycle/greatest) for automated testing
|
2016-01-28 16:31:32 -05:00 |
|