README: note how bash's own errors appear in case output.
commit 29dc7c3cabdf6bdf9ad3b6553436cec5da733310 · parent 3b20fba208
· browse this tree
Ximianth, 2026-10-25 09:50:28 UTC
diff --git a/README.md b/README.md index d58e490..435921a 100644 --- a/README.md +++ b/README.md @@ -76,6 +76,7 @@ Each case runs it in a fresh bash, so it's a clean shell: - stdin is the trigger hunk's body, exactly. - `set -euo pipefail` is on. A failing command stops the case, and the failure shows up in its output. + Bash's own error messages there are labeled with the function's name, nothing more, so they read the same wherever the test runs. - The working directory is the test script's, so a relative path like `./mytool` works, wherever the test is run from. - It sees exported variables (like `PATH`), but no other variables, and no other functions. If it calls helpers, pass them to `testmarktest_provide helper1 helper2` first.