Put in unit tests to catch parser failure

Noticed that the reader could over-consume “NaN” if token terminated in the middle.

Put in unit tests to catch parser failure
Noticed that the reader could over-consume “NaN” if token terminated in the middle.
c4117c68 · StilesCrisis · 933eb839 · c4117c68
Commit c4117c68 authored Feb 23, 2017 by StilesCrisis
Hide whitespace changes
Inline Side-by-side

Showing with 4 additions and 0 deletions

readertest.cpp test/unittest/readertest.cpp +4 -0

No files found.
--- a/test/unittest/readertest.cpp
+++ b/test/unittest/readertest.cpp
@@ -1832,6 +1832,10 @@ TEST(Reader, ParseNanAndInfinity) {
    TEST_NAN_INF("Infinity", inf);
    TEST_NAN_INF("-Inf", -inf);
    TEST_NAN_INF("-Infinity", -inf);
+    TEST_NAN_INF_ERROR(kParseErrorValueInvalid, "NInf", 1);
+    TEST_NAN_INF_ERROR(kParseErrorValueInvalid, "NaInf", 1);
+    TEST_NAN_INF_ERROR(kParseErrorValueInvalid, "INan", 1);
+    TEST_NAN_INF_ERROR(kParseErrorValueInvalid, "InNan", 1);
    TEST_NAN_INF_ERROR(kParseErrorValueInvalid, "nan", 1);
    TEST_NAN_INF_ERROR(kParseErrorValueInvalid, "-nan", 1);
    TEST_NAN_INF_ERROR(kParseErrorValueInvalid, "NAN", 1);