add new assert_no_diff assertion directive #82
Merged
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
a regular action when testing scripts is to test generated files to match a valid content. This is often done using assert with the following line: assert "diff 'path/to/exepected file' 'path/to/generated file'" newly assertion tool assert_no_diff makes intention clearer by using the following syntax: assert_no_diff "path/to/expected file" "path/to/generated file" goal is to make clearer the facts that: - what is expected is that there is no difference - what is compared are two files
env usage in shebang line was not compatible with env as provided by coreutils 9.0. If arguments are to be passed to the command given to env, -S option is to be used.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
a regular action when testing scripts is to test generated files to match a valid content. This is often done using assert with the following line:
assert "diff 'path/to/exepected file' 'path/to/generated file'"newly assertion tool assert_no_diff makes intention clearer by using the following syntax:
assert_no_diff "path/to/expected file" "path/to/generated file"goal is to make visible that: