Unit tests volkszaehler api_parse_exception #88
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I added #89 as bug for the issues highlighted. |
r00t-
added a commit
that referenced
this pull request
Dec 30, 2014
Unit tests volkszaehler api_parse_exception
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To increase the test depth before changing libjson (see #82, #72) I added some unit tests to api_parse_exception.
Those tests highlight some significant bugs (in the orig. code, not due to #82) which can lead to memory corruptions and vzlogger crashes. Till now not fixed but just added reminders "todo".