Support Bash "strict mode" (and fix one unit test) #239
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 few different kinds of changes are made:
- Optional parameters/variables are changed to ${var-} to default to
empty or given defaults with ${var=...}.
- ((...)) arithmetic evaluation "fails" when the result happens to be
zero, so silence this with "|| true"
This will help ensure that bashunit won't cause problems with tests that use "set -euo pipefail"
Watermelon AI SummaryAI Summary deactivated by djpohly GitHub PRs
bashunit is an open repo and Watermelon will serve it for free. |
antonio-gg-dev
requested review from
Chemaclass,
antonio-gg-dev,
cmayo and
khru
Chemaclass
approved these changes
Dec 22, 2023
Member
Chemaclass
left a comment
Chemaclass
left a comment
There was a problem hiding this comment.
Wow, this is pretty cool. Thanks!
Member
|
It seems that it is not working as expected for macos... I will check it out when I find some time these days |
Member
|
I will merge this branch into an internal one with the same name |
carlfriedrich
added a commit
to carlfriedrich/testing-in-bash
that referenced
this pull request
Aug 21, 2025
Support for Bash strict mode has been added in 0.14: https://bashunit.typeddevs.com/blog/2024-07-14-release-0-14#%F0%9F%8C%BE-miscellaneous TypedDevs/bashunit#239 CI compatible report (JUnit XML format) has been added in 0.14: https://bashunit.typeddevs.com/blog/2024-07-14-release-0-14#logger-junit-xml https://bashunit.typeddevs.com/command-line#junit-logging Parallel execution has been added in 0.18: https://bashunit.typeddevs.com/blog/2024-10-16-release-0-18#running-in-parallel-358
carlfriedrich
added a commit
to carlfriedrich/testing-in-bash
that referenced
this pull request
Aug 21, 2025
Support for Bash strict mode has been added in 0.14: https://bashunit.typeddevs.com/blog/2024-07-14-release-0-14#%F0%9F%8C%BE-miscellaneous TypedDevs/bashunit#239 CI compatible report (JUnit XML format) has been added in 0.14: https://bashunit.typeddevs.com/blog/2024-07-14-release-0-14#logger-junit-xml https://bashunit.typeddevs.com/command-line#junit-logging Parallel execution has been added in 0.18: https://bashunit.typeddevs.com/blog/2024-10-16-release-0-18#running-in-parallel-358 Mocking is avaliable and the previously linked issue has been merged in 0.20: https://bashunit.typeddevs.com/test-doubles#mock TypedDevs/bashunit#232
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.
📚 Description
Some script authors like to use "unofficial Bash strict mode", enough so that supporting it shows up in comparisons of shell testing frameworks.
Case in point: enabling the -u option uncovered a bug in
test_unsuccessful_assert_is_directory_not_writablethat is fixed in this PR.🔖 Changes
set -euo pipefailenabled.$a_filewas supposed to be$a_directory).((...)), which exit 1 if their result happens to be zero, are fixed with|| true.check_duplicate_functionsdoes not appear to be intended to cause the script to fail, so it is also silenced with|| true.${1-}."${varname=default}".set_up) will not be run instead.✅ To-do list
CHANGELOG.mdto reflect the new feature or fixI updated the documentation to reflect the changes(Not sure there's anything to document, since this fix doesn't require users to do anything different.)