jsnapy 1.3.8 release update #419
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
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.
What does this PR do?
JSNPy 1.3.8 release update
What issues does this PR fix or reference?
Bugs Fixed:
Fixed jsnap2py #327
Fixed user-specified info/error message. Messages are updated in the results for test operator "exists" #393
Fixed handling empty or missing pre or post-snapshots for test operator "no_diff" #413
Fixed to handle device instance when the mode is telnet and port is 23 #535
Fixed typos for PRE and POST keys in the node_value_passed of not_exists operator #410
Fixed calling jsnapy without username and password which causes exception instead of prompt #400
Tests written?
Yes/No