fix bug in integration test harness that errored on new module#1506
Merged
Conversation
the test harness was designed to grab git commit info to include with the various files that it creates to keep track of testing versions. these test scripts assumed that the module being tested against had been committed to git already, but i run into an error because i was trying to test a local module that i had not yet added to git. this checks for that and gracefully moves forward.
add doc strings and fix some of the linter errors
Collaborator
Author
|
I added a bunch of doc strings and fixed some of the linter errors. its ready now. |
This file contains hidden or 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
1 participant
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.
the test harness was designed to grab git commit info to include with the various files that it creates to keep track of testing versions. these test scripts assumed that the module being tested against had been committed to git already, but i run into an error because i was trying to test a local module that i had not yet added to git. this checks for that and gracefully moves forward.