CLI tests #162
Merged
CLI tests #162
Conversation
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
|
Force push because I accidentally committed my test file in a9b769d |
acdha
approved these changes
Oct 20, 2022
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.
This is for #161
I ended up noticing a couple of bugs and unclear behaviors, mostly around completeness tests. I changed the requirement for
--processesto 1 or more since setting it to 0 make multiproccesing throw errors. I also changed the error message for failed completeness validations toBag is incompleteto differentiate it from failed hash validations.The tests are a bit verbose and use nested
with's to capture the different outputs. If there is a cleaner way, I'm happy to use that instead.