Skip to content

tests: Improve CharReaderFailIfExtraTest #1011

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

res2k
Copy link
Contributor

@res2k res2k commented Aug 21, 2019

  • There was a nonsensical change of 'failIfExtra' before calling strictMode():
    the latter resets the former.
    Dealt with by having one test with pure strictMode and one with strictMode
    but failIfExtra=false.
  • The JSONTEST_ASSERT_STRING_EQUAL tests for the error strings swapped
    the 'expected' and 'actual' values.

* There was a nonsensical change of 'failIfExtra' before calling strictMode():
  the latter resets the former.
  Dealt with by having one test with pure strictMode and one with strictMode
  but failIfExtra=false.
* The JSONTEST_ASSERT_STRING_EQUAL tests for the error strings swapped
  the 'expected' and 'actual' values.
@baylesj baylesj merged commit b941149 into open-source-parsers:master Aug 26, 2019
dawesc pushed a commit to EFTlab/jsoncpp that referenced this pull request Sep 25, 2019
* There was a nonsensical change of 'failIfExtra' before calling strictMode():
  the latter resets the former.
  Dealt with by having one test with pure strictMode and one with strictMode
  but failIfExtra=false.
* The JSONTEST_ASSERT_STRING_EQUAL tests for the error strings swapped
  the 'expected' and 'actual' values.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants