Merge branch 'main' into fix-test-doubles

 Conflicts:
	tests/functional/doubles_test.sh

Author: Chemaclass

.env.example

@@ -11,4 +11,3 @@ BASHUNIT_HEADER_ASCII_ART=
 BASHUNIT_SIMPLE_OUTPUT=
 BASHUNIT_STOP_ON_FAILURE=
 BASHUNIT_SHOW_EXECUTION_TIME=
-BASHUNIT_DEV_MODE=

.github/workflows/tests.yml

@@ -42,7 +42,7 @@ jobs:
       - name: Run tests
         shell: bash
         run: |
-          ./bashunit tests/${{ matrix.test_chunk }}/*_test.sh
+          ./bashunit --parallel tests/${{ matrix.test_chunk }}/*_test.sh
 
   alpine:
     name: "On alpine-latest"

CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## Unreleased
+
+- Fix asserts on test doubles in subshell
+- Allow interpolating arguments in data providers output
+- Deprecate `# data_provider` in favor of `# @data_provider`
+- Allow `assert_have_been_called_with` to check arguments of specific calls
+- Enable parallel tests on Windows
+- Add `assert_not_called`
+- Improve `find_total_tests` performance
+
+## [0.19.1](https://github.com/TypedDevs/bashunit/compare/0.19.0...0.19.1) - 2025-05-23
+
+- Replace `#!/bin/bash` with `#!/usr/bin/env bash`
+- Usage printf with awk, which correctly handles float rounding and improves portability
+
+## [0.19.0](https://github.com/TypedDevs/bashunit/compare/0.18.0...0.19.0) - 2025-02-19
+
+- Fixed false negative with `set -e`
+- Fixed name rendered when having `test_test_*`
+- Fixed duplicate function detection
+- Fixed display test with multiple outputs in multiline
+- Improved output: adding a space between each test file
+- Removed `BASHUNIT_DEV_MODE` in favor of `BASHUNIT_DEV_LOG`
+- Added source file and line on global dev function `log`
+
 ## [0.18.0](https://github.com/TypedDevs/bashunit/compare/0.17.0...0.18.0) - 2024-10-16
 
 - Added `-p|--parallel` to enable running tests in parallel

adrs/adr-004-metadata-prefix.md

@@ -0,0 +1,37 @@
+# Title: Prefix metadata comments with @
+
+* Status: accepted
+* Authors: @Chemaclass
+* Date: 2025-05-29
+
+
+## Context and Problem Statement
+
+Data providers are defined via a special comment `# data_provider`. We want to
+clearly differentiate these meta comments from ordinary comments.
+
+## Considered Options
+
+* Keep using `# data_provider` as is.
+* Introduce an `@` prefix for special comments while supporting the old syntax.
+
+## Decision Outcome
+
+We decided to prefix the metadata provider directives with `@`,
+eg: using `# @data_provider provider_name`.
+
+> The previous form without the prefix is still supported for backward compatibility but is now deprecated.
+
+### Positive Consequences
+
+* Highlights special bashunit directives clearly.
+* Allows future directives to consistently use the `@` prefix.
+
+### Negative Consequences
+
+* Projects must eventually update old comments to the new syntax.
+
+## Technical Details
+
+`helper::get_provider_data` now matches both `# @data_provider` and the old
+`# data_provider` when locating provider functions.

bashunit

@@ -1,8 +1,8 @@
-#!/bin/bash
+#!/usr/bin/env bash
 set -euo pipefail
 
 # shellcheck disable=SC2034
-declare -r BASHUNIT_VERSION="0.18.0"
+declare -r BASHUNIT_VERSION="0.19.1"
 
 # shellcheck disable=SC2155
 declare -r BASHUNIT_ROOT_DIR="$(dirname "${BASH_SOURCE[0]}")"

bin/pre-commit

@@ -1,4 +1,4 @@
-#!/bin/bash
+#!/usr/bin/env bash
 echo "Running pre-commit checks"
 
 make pre_commit/run

build.sh

@@ -1,4 +1,4 @@
-#!/bin/bash
+#!/usr/bin/env bash
 
 source src/check_os.sh
 
@@ -37,7 +37,7 @@ function build::generate_bin() {
   local temp
   temp="$(dirname "$out")/temp.sh"
 
-  echo '#!/bin/bash' > "$temp"
+  echo '#!/usr/bin/env bash' > "$temp"
   echo "Generating bashunit in the '$(dirname "$out")' folder..."
 
   for file in $(build::dependencies); do

docs/blog/2024-09-01-release-0-15.md

@@ -51,7 +51,7 @@ BASHUNIT_REPORT_HTML=
 
 ::: code-group
 ```bash [example_test.sh]
-# data_provider provider_directories
+# @data_provider provider_directories
 function test_directory_exists() {
   local outro=$1
   local directory=$2

docs/command-line.md

@@ -129,6 +129,12 @@ Creates a report XML file that follows the JUnit XML format and contains informa
 
 bashunit provides an option to run each test in a separate child process, allowing you to parallelize the test execution and potentially speed up the testing process. When running in parallel mode, the execution order of tests is randomized.
 
+::: warning
+Parallel mode is supported on **macOS**, **Ubuntu**, and **Windows**. On other
+systems (like Alpine Linux) the option is automatically disabled due to
+inconsistent results. In those environments consider using `--no-parallel`.
+:::
+
 ::: code-group
 ```bash [Example]
 ./bashunit ./tests --parallel
@@ -304,7 +310,6 @@ BASHUNIT_HEADER_ASCII_ART:    false
 BASHUNIT_SIMPLE_OUTPUT:       false
 BASHUNIT_STOP_ON_FAILURE:     false
 BASHUNIT_SHOW_EXECUTION_TIME: true
-BASHUNIT_DEV_MODE:            true
 BASHUNIT_VERBOSE:             true
 ########################################################################################################################################
 

docs/configuration.md

@@ -68,6 +68,11 @@ BASHUNIT_SIMPLE_OUTPUT=false
 
 Runs the tests in child processes with randomized execution, which may improve overall testing speed, especially for larger test suites.
 
+::: warning
+Parallel execution is supported only on **macOS** and **Ubuntu**. On other
+systems bashunit forces sequential execution to avoid inconsistent results.
+:::
+
 Similar as using `-p|--parallel` option on the [command line](/command-line#parallel).