refactor(tests): mirror the src/ module layout in tests/unit/

[Chemaclass]

🤔 Background

Closes#957. tests/unit/ was 71 flat files with the module encoded in a filename prefix; src/ has been 17 modules since #948.

tests/unit/coverage/engine_test.sh for src/coverage/engine.sh
tests/unit/runner/exec_test.sh for src/runner/exec.sh

16 directories named for their source module, plus tests/unit/project/ for the ten tests covering the repo's own tooling and invariants (the five release_*, package_json, build, bash_version, bash_compatibility, redirect_error) — naming that honestly beats filing them under a module name that would be a lie.

⚠️ Three classes of breakage, all found by running rather than reading

1. Fifteen tests resolve paths from their own location. Moving them one level deeper broke $(bashunit::current_dir)/fixtures/.... Fixtures stay shared at tests/unit/fixtures/, so those become ../fixtures/. The four find_files_recursive tests now take a repo-relative input instead — a ../ in the input reappears in the output they assert on.

2. Snapshots had to move and be renamed with their test — and two were already poisoned. The failing runs had auto-recorded them at the new path (documented behaviour: a missing snapshot gets written). For the two "unsuccessful" cases they captured Expected snapshot instead of Actual snapshot text — those tests exist to demonstrate a mismatch, so keeping the auto-recorded files would have silently inverted them. Originals restored and diffed.

3. Renaming introduced three duplicate basenames, which cost 52 tests under --parallel.

🐛 That third one is a real bashunit bug — #959

src/runner/result.sh:28 buckets per-test results by basename, so a/foo_test.sh and b/foo_test.sh share a bucket and overwrite each other. Silently, and green.

	--parallel --simple --strict
with 3 duplicate basenames	1536
after renaming them unique	1588

Same class as #923, which fixed exactly this in build.sh. It affects any user project whose tests mirror a source tree — the layout this very PR adopts. Worked around here by keeping basenames unique; the fix belongs to #959.

✅ Verification

The number this whole issue was designed around:

• sequential: 1629 before and after — nothing lost
• --parallel --simple --strict: 1588 = the 1585 baseline + the 3 collection-guard tests from build(make): collect tests recursively so tests/ can mirror src/ #958
• make test collects the same set as ./bashunit tests/, enforced by the guard

Green: make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅.

[Chemaclass]

🤔 Background

Closes#957. tests/unit/ was 71 flat files with the module encoded in a filename prefix; src/ has been 17 modules since #948.

tests/unit/coverage/engine_test.sh for src/coverage/engine.sh
tests/unit/runner/exec_test.sh for src/runner/exec.sh

16 directories named for their source module, plus tests/unit/project/ for the ten tests covering the repo's own tooling and invariants (the five release_*, package_json, build, bash_version, bash_compatibility, redirect_error) — naming that honestly beats filing them under a module name that would be a lie.

⚠️ Three classes of breakage, all found by running rather than reading

1. Fifteen tests resolve paths from their own location. Moving them one level deeper broke $(bashunit::current_dir)/fixtures/.... Fixtures stay shared at tests/unit/fixtures/, so those become ../fixtures/. The four find_files_recursive tests now take a repo-relative input instead — a ../ in the input reappears in the output they assert on.

2. Snapshots had to move and be renamed with their test — and two were already poisoned. The failing runs had auto-recorded them at the new path (documented behaviour: a missing snapshot gets written). For the two "unsuccessful" cases they captured Expected snapshot instead of Actual snapshot text — those tests exist to demonstrate a mismatch, so keeping the auto-recorded files would have silently inverted them. Originals restored and diffed.

3. Renaming introduced three duplicate basenames, which cost 52 tests under --parallel.

🐛 That third one is a real bashunit bug — #959

src/runner/result.sh:28 buckets per-test results by basename, so a/foo_test.sh and b/foo_test.sh share a bucket and overwrite each other. Silently, and green.

	--parallel --simple --strict
with 3 duplicate basenames	1536
after renaming them unique	1588

Same class as #923, which fixed exactly this in build.sh. It affects any user project whose tests mirror a source tree — the layout this very PR adopts. Worked around here by keeping basenames unique; the fix belongs to #959.

✅ Verification

The number this whole issue was designed around:

• sequential: 1629 before and after — nothing lost
• --parallel --simple --strict: 1588 = the 1585 baseline + the 3 collection-guard tests from build(make): collect tests recursively so tests/ can mirror src/ #958
• make test collects the same set as ./bashunit tests/, enforced by the guard

Green: make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅.

[Chemaclass]

🤔 Background

Closes#957. tests/unit/ was 71 flat files with the module encoded in a filename prefix; src/ has been 17 modules since #948.

tests/unit/coverage/engine_test.sh for src/coverage/engine.sh
tests/unit/runner/exec_test.sh for src/runner/exec.sh

16 directories named for their source module, plus tests/unit/project/ for the ten tests covering the repo's own tooling and invariants (the five release_*, package_json, build, bash_version, bash_compatibility, redirect_error) — naming that honestly beats filing them under a module name that would be a lie.

⚠️ Three classes of breakage, all found by running rather than reading

1. Fifteen tests resolve paths from their own location. Moving them one level deeper broke $(bashunit::current_dir)/fixtures/.... Fixtures stay shared at tests/unit/fixtures/, so those become ../fixtures/. The four find_files_recursive tests now take a repo-relative input instead — a ../ in the input reappears in the output they assert on.

2. Snapshots had to move and be renamed with their test — and two were already poisoned. The failing runs had auto-recorded them at the new path (documented behaviour: a missing snapshot gets written). For the two "unsuccessful" cases they captured Expected snapshot instead of Actual snapshot text — those tests exist to demonstrate a mismatch, so keeping the auto-recorded files would have silently inverted them. Originals restored and diffed.

3. Renaming introduced three duplicate basenames, which cost 52 tests under --parallel.

🐛 That third one is a real bashunit bug — #959

src/runner/result.sh:28 buckets per-test results by basename, so a/foo_test.sh and b/foo_test.sh share a bucket and overwrite each other. Silently, and green.

	--parallel --simple --strict
with 3 duplicate basenames	1536
after renaming them unique	1588

Same class as #923, which fixed exactly this in build.sh. It affects any user project whose tests mirror a source tree — the layout this very PR adopts. Worked around here by keeping basenames unique; the fix belongs to #959.

✅ Verification

The number this whole issue was designed around:

• sequential: 1629 before and after — nothing lost
• --parallel --simple --strict: 1588 = the 1585 baseline + the 3 collection-guard tests from build(make): collect tests recursively so tests/ can mirror src/ #958
• make test collects the same set as ./bashunit tests/, enforced by the guard

Green: make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅.

[Chemaclass]

🤔 Background

Closes#957. tests/unit/ was 71 flat files with the module encoded in a filename prefix; src/ has been 17 modules since #948.

tests/unit/coverage/engine_test.sh for src/coverage/engine.sh
tests/unit/runner/exec_test.sh for src/runner/exec.sh

16 directories named for their source module, plus tests/unit/project/ for the ten tests covering the repo's own tooling and invariants (the five release_*, package_json, build, bash_version, bash_compatibility, redirect_error) — naming that honestly beats filing them under a module name that would be a lie.

⚠️ Three classes of breakage, all found by running rather than reading

1. Fifteen tests resolve paths from their own location. Moving them one level deeper broke $(bashunit::current_dir)/fixtures/.... Fixtures stay shared at tests/unit/fixtures/, so those become ../fixtures/. The four find_files_recursive tests now take a repo-relative input instead — a ../ in the input reappears in the output they assert on.

2. Snapshots had to move and be renamed with their test — and two were already poisoned. The failing runs had auto-recorded them at the new path (documented behaviour: a missing snapshot gets written). For the two "unsuccessful" cases they captured Expected snapshot instead of Actual snapshot text — those tests exist to demonstrate a mismatch, so keeping the auto-recorded files would have silently inverted them. Originals restored and diffed.

3. Renaming introduced three duplicate basenames, which cost 52 tests under --parallel.

🐛 That third one is a real bashunit bug — #959

src/runner/result.sh:28 buckets per-test results by basename, so a/foo_test.sh and b/foo_test.sh share a bucket and overwrite each other. Silently, and green.

	--parallel --simple --strict
with 3 duplicate basenames	1536
after renaming them unique	1588

Same class as #923, which fixed exactly this in build.sh. It affects any user project whose tests mirror a source tree — the layout this very PR adopts. Worked around here by keeping basenames unique; the fix belongs to #959.

✅ Verification

The number this whole issue was designed around:

• sequential: 1629 before and after — nothing lost
• --parallel --simple --strict: 1588 = the 1585 baseline + the 3 collection-guard tests from build(make): collect tests recursively so tests/ can mirror src/ #958
• make test collects the same set as ./bashunit tests/, enforced by the guard

Green: make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅.

[Chemaclass]

🤔 Background

Closes#957. tests/unit/ was 71 flat files with the module encoded in a filename prefix; src/ has been 17 modules since #948.

tests/unit/coverage/engine_test.sh for src/coverage/engine.sh
tests/unit/runner/exec_test.sh for src/runner/exec.sh

16 directories named for their source module, plus tests/unit/project/ for the ten tests covering the repo's own tooling and invariants (the five release_*, package_json, build, bash_version, bash_compatibility, redirect_error) — naming that honestly beats filing them under a module name that would be a lie.

⚠️ Three classes of breakage, all found by running rather than reading

1. Fifteen tests resolve paths from their own location. Moving them one level deeper broke $(bashunit::current_dir)/fixtures/.... Fixtures stay shared at tests/unit/fixtures/, so those become ../fixtures/. The four find_files_recursive tests now take a repo-relative input instead — a ../ in the input reappears in the output they assert on.

2. Snapshots had to move and be renamed with their test — and two were already poisoned. The failing runs had auto-recorded them at the new path (documented behaviour: a missing snapshot gets written). For the two "unsuccessful" cases they captured Expected snapshot instead of Actual snapshot text — those tests exist to demonstrate a mismatch, so keeping the auto-recorded files would have silently inverted them. Originals restored and diffed.

3. Renaming introduced three duplicate basenames, which cost 52 tests under --parallel.

🐛 That third one is a real bashunit bug — #959

src/runner/result.sh:28 buckets per-test results by basename, so a/foo_test.sh and b/foo_test.sh share a bucket and overwrite each other. Silently, and green.

	--parallel --simple --strict
with 3 duplicate basenames	1536
after renaming them unique	1588

Same class as #923, which fixed exactly this in build.sh. It affects any user project whose tests mirror a source tree — the layout this very PR adopts. Worked around here by keeping basenames unique; the fix belongs to #959.

✅ Verification

The number this whole issue was designed around:

• sequential: 1629 before and after — nothing lost
• --parallel --simple --strict: 1588 = the 1585 baseline + the 3 collection-guard tests from build(make): collect tests recursively so tests/ can mirror src/ #958
• make test collects the same set as ./bashunit tests/, enforced by the guard

Green: make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅.

[Chemaclass]

🤔 Background

Closes#957. tests/unit/ was 71 flat files with the module encoded in a filename prefix; src/ has been 17 modules since #948.

tests/unit/coverage/engine_test.sh for src/coverage/engine.sh
tests/unit/runner/exec_test.sh for src/runner/exec.sh

16 directories named for their source module, plus tests/unit/project/ for the ten tests covering the repo's own tooling and invariants (the five release_*, package_json, build, bash_version, bash_compatibility, redirect_error) — naming that honestly beats filing them under a module name that would be a lie.

⚠️ Three classes of breakage, all found by running rather than reading

1. Fifteen tests resolve paths from their own location. Moving them one level deeper broke $(bashunit::current_dir)/fixtures/.... Fixtures stay shared at tests/unit/fixtures/, so those become ../fixtures/. The four find_files_recursive tests now take a repo-relative input instead — a ../ in the input reappears in the output they assert on.

2. Snapshots had to move and be renamed with their test — and two were already poisoned. The failing runs had auto-recorded them at the new path (documented behaviour: a missing snapshot gets written). For the two "unsuccessful" cases they captured Expected snapshot instead of Actual snapshot text — those tests exist to demonstrate a mismatch, so keeping the auto-recorded files would have silently inverted them. Originals restored and diffed.

3. Renaming introduced three duplicate basenames, which cost 52 tests under --parallel.

🐛 That third one is a real bashunit bug — #959

src/runner/result.sh:28 buckets per-test results by basename, so a/foo_test.sh and b/foo_test.sh share a bucket and overwrite each other. Silently, and green.

	--parallel --simple --strict
with 3 duplicate basenames	1536
after renaming them unique	1588

Same class as #923, which fixed exactly this in build.sh. It affects any user project whose tests mirror a source tree — the layout this very PR adopts. Worked around here by keeping basenames unique; the fix belongs to #959.

✅ Verification

The number this whole issue was designed around:

• sequential: 1629 before and after — nothing lost
• --parallel --simple --strict: 1588 = the 1585 baseline + the 3 collection-guard tests from build(make): collect tests recursively so tests/ can mirror src/ #958
• make test collects the same set as ./bashunit tests/, enforced by the guard

Green: make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅.

[Chemaclass]

🤔 Background

Closes#957. tests/unit/ was 71 flat files with the module encoded in a filename prefix; src/ has been 17 modules since #948.

tests/unit/coverage/engine_test.sh for src/coverage/engine.sh
tests/unit/runner/exec_test.sh for src/runner/exec.sh

16 directories named for their source module, plus tests/unit/project/ for the ten tests covering the repo's own tooling and invariants (the five release_*, package_json, build, bash_version, bash_compatibility, redirect_error) — naming that honestly beats filing them under a module name that would be a lie.

⚠️ Three classes of breakage, all found by running rather than reading

1. Fifteen tests resolve paths from their own location. Moving them one level deeper broke $(bashunit::current_dir)/fixtures/.... Fixtures stay shared at tests/unit/fixtures/, so those become ../fixtures/. The four find_files_recursive tests now take a repo-relative input instead — a ../ in the input reappears in the output they assert on.

2. Snapshots had to move and be renamed with their test — and two were already poisoned. The failing runs had auto-recorded them at the new path (documented behaviour: a missing snapshot gets written). For the two "unsuccessful" cases they captured Expected snapshot instead of Actual snapshot text — those tests exist to demonstrate a mismatch, so keeping the auto-recorded files would have silently inverted them. Originals restored and diffed.

3. Renaming introduced three duplicate basenames, which cost 52 tests under --parallel.

🐛 That third one is a real bashunit bug — #959

src/runner/result.sh:28 buckets per-test results by basename, so a/foo_test.sh and b/foo_test.sh share a bucket and overwrite each other. Silently, and green.

	--parallel --simple --strict
with 3 duplicate basenames	1536
after renaming them unique	1588

Same class as #923, which fixed exactly this in build.sh. It affects any user project whose tests mirror a source tree — the layout this very PR adopts. Worked around here by keeping basenames unique; the fix belongs to #959.

✅ Verification

The number this whole issue was designed around:

• sequential: 1629 before and after — nothing lost
• --parallel --simple --strict: 1588 = the 1585 baseline + the 3 collection-guard tests from build(make): collect tests recursively so tests/ can mirror src/ #958
• make test collects the same set as ./bashunit tests/, enforced by the guard

Green: make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅.

[Chemaclass]

🤔 Background

Closes#957. tests/unit/ was 71 flat files with the module encoded in a filename prefix; src/ has been 17 modules since #948.

tests/unit/coverage/engine_test.sh for src/coverage/engine.sh
tests/unit/runner/exec_test.sh for src/runner/exec.sh

16 directories named for their source module, plus tests/unit/project/ for the ten tests covering the repo's own tooling and invariants (the five release_*, package_json, build, bash_version, bash_compatibility, redirect_error) — naming that honestly beats filing them under a module name that would be a lie.

⚠️ Three classes of breakage, all found by running rather than reading

1. Fifteen tests resolve paths from their own location. Moving them one level deeper broke $(bashunit::current_dir)/fixtures/.... Fixtures stay shared at tests/unit/fixtures/, so those become ../fixtures/. The four find_files_recursive tests now take a repo-relative input instead — a ../ in the input reappears in the output they assert on.

2. Snapshots had to move and be renamed with their test — and two were already poisoned. The failing runs had auto-recorded them at the new path (documented behaviour: a missing snapshot gets written). For the two "unsuccessful" cases they captured Expected snapshot instead of Actual snapshot text — those tests exist to demonstrate a mismatch, so keeping the auto-recorded files would have silently inverted them. Originals restored and diffed.

3. Renaming introduced three duplicate basenames, which cost 52 tests under --parallel.

🐛 That third one is a real bashunit bug — #959

src/runner/result.sh:28 buckets per-test results by basename, so a/foo_test.sh and b/foo_test.sh share a bucket and overwrite each other. Silently, and green.

	--parallel --simple --strict
with 3 duplicate basenames	1536
after renaming them unique	1588

Same class as #923, which fixed exactly this in build.sh. It affects any user project whose tests mirror a source tree — the layout this very PR adopts. Worked around here by keeping basenames unique; the fix belongs to #959.

✅ Verification

The number this whole issue was designed around:

• sequential: 1629 before and after — nothing lost
• --parallel --simple --strict: 1588 = the 1585 baseline + the 3 collection-guard tests from build(make): collect tests recursively so tests/ can mirror src/ #958
• make test collects the same set as ./bashunit tests/, enforced by the guard

Green: make sa · make lint · bash build.sh bin -v → ✅ Build verified ✅.