Release 0.29.0

Monday, December 8, 2025

🔧 New features

Namespaced internal functions

All internal functions and variables are now prefixed with bashunit:: to prevent naming collisions with your code:

Before

skip "reason"
helper::trim "$value"

After

bashunit::skip "reason"
bashunit::helper::trim "$value"

Internal variables are also prefixed: _TESTS_PASSED becomes _BASHUNIT_TESTS_PASSED. The public API (assert_* functions) remains unchanged.

Bootstrap argument passing

Pass arguments to your bootstrap script using the --env flag:

Usage

bashunit --env "bootstrap.sh arg1 arg2" tests/

Environment variable

BASHUNIT_BOOTSTRAP_ARGS="arg1 arg2" bashunit tests/

Login shell support

Run tests in a login shell context with the new -l, --login flag:

Usage

bashunit --login tests/

This loads your shell profile, useful when testing scripts that depend on login shell configuration.

Strict mode

Enable strict shell mode (set -euo pipefail) for your tests:

Usage

bashunit --strict tests/

Configuration

BASHUNIT_STRICT_MODE=true

Strict mode catches unset variables and pipeline failures, helping you write more robust scripts.

Run all assertions

Override the default stop-on-failure behavior with -R, --run-all:

Usage

bashunit --run-all tests/

Standalone assert subcommand

Use assertions directly from the command line:

Usage

bashunit assert equals "expected" "actual"
bashunit assert contains "needle" "haystack"

🐛 Bug fixes

• Custom assertions now display correct test function name in failure messages
• Data providers work when set_up_before_script changes directory
• Resolved race conditions in parallel test execution
• Test doubles are now strict mode compatible
• Catch intermediate failing commands in set_up_before_script and tear_down_after_script

🌾 Miscellaneous

• Improved assert command output: shows assert <fn> instead of internal function name
• --preserve-env option to skip .env loading and use shell environment only

---

See the full changelog on GitHub