build(make): collect tests recursively so tests/ can mirror src/ by Chemaclass · Pull Request #958 · TypedDevs/bashunit

Chemaclass · 2026-08-01T18:02:51Z

🤔 Background

Related #957 — prerequisite for every PR in that issue.

src/ is 17 modules with no loose files. tests/unit/ is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs make test to find nested tests first.

⚠️ The problem this prevents

Makefile:67 collected with $(wildcard tests/*/*[tT]est.sh) — exactly one level. ./bashunit tests/ already recurses (verified). So the moment a test is nested, three of the four CI matrix entries would run it and make test would silently skip it — green, and quietly testing less.

💡 Why "just make it recursive" is wrong

A naive recursive glob also collects four files under fixtures/ that are inputs to other tests, not tests:

tests/acceptance/fixtures/tests_path/{a,other}_test.sh
tests/unit/fixtures/tests/example{1,2}_test.sh

So fixtures/ is excluded by path. Collection is unchanged today — the same 156 files, verified byte-for-byte against the old glob's output. This PR moves nothing; it only makes nesting possible.

✅ The guard

tests/unit/project/collection_test.sh — itself nested, so the old glob wouldn't have collected it. Three assertions:

every test file on disk reaches make test
no fixture does
fixtures that would be swept in still exist — so assertion 2 can't pass vacuously

Both failure modes mutation-verified: reverting to the one-level glob reddens the first, dropping the fixtures/ exclusion reddens the second.

✅ Verification

Suite total 1626 → 1629 — exactly the three new tests, nothing lost.

(make test reports a different total from ./bashunit tests/ for pre-existing mode-dependent skips, not collection differences — which is why the guard compares file lists rather than totals.)

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

Prerequisite for #957. src/ is seventeen modules with no loose files; tests/unit is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs `make test` to find nested tests first. The Makefile collected with $(wildcard tests/*/*[tT]est.sh), which matches exactly one level. `./bashunit tests/` already recurses, so a nested test would have been run by three of the four CI matrix entries and silently skipped by `make test` -- green, and quietly testing less. Recursive collection alone is not the fix. A naive recursive glob also picks up four files under fixtures/ that are inputs to other tests rather than tests: tests/acceptance/fixtures/tests_path/{a,other}_test.sh tests/unit/fixtures/tests/example{1,2}_test.sh so fixtures/ is excluded by path. Collection is unchanged today: the same 156 files, byte for byte, verified against the old glob's output. tests/unit/project/collection_test.sh keeps it honest, and is itself nested -- the old glob would not have collected it. It asserts that every test file on disk reaches `make test`, that no fixture does, and that fixtures which would be swept in still exist, so the second assertion cannot pass vacuously. Both failure modes were verified by mutation: reverting to the one-level glob reddens the first test, dropping the fixtures exclusion reddens the second. The suite total goes 1626 -> 1629, which is exactly the three new tests.

Run from inside `make test`, the sub-make in collection_from_make inherits MAKEFLAGS and wraps its output in `make[1]: Entering/Leaving directory`. The positional `tail -n +2` stripped the Entering line instead of the header, so the comparison saw both the header and the trailing Leaving line and failed on the four make-driven CI jobs while every `./bashunit tests/` job passed. Filter on a `tests/` prefix instead of stripping a fixed number of lines, and clear MAKEFLAGS so the sub-make cannot inherit -j or a parent goal. Reproduced locally by running the guard through a wrapper Makefile, which fails before this change and passes after.

Chemaclass · 2026-08-01T18:02:51Z

🤔 Background

Related #957 — prerequisite for every PR in that issue.

src/ is 17 modules with no loose files. tests/unit/ is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs make test to find nested tests first.

⚠️ The problem this prevents

Makefile:67 collected with $(wildcard tests/*/*[tT]est.sh) — exactly one level. ./bashunit tests/ already recurses (verified). So the moment a test is nested, three of the four CI matrix entries would run it and make test would silently skip it — green, and quietly testing less.

💡 Why "just make it recursive" is wrong

A naive recursive glob also collects four files under fixtures/ that are inputs to other tests, not tests:

tests/acceptance/fixtures/tests_path/{a,other}_test.sh
tests/unit/fixtures/tests/example{1,2}_test.sh

So fixtures/ is excluded by path. Collection is unchanged today — the same 156 files, verified byte-for-byte against the old glob's output. This PR moves nothing; it only makes nesting possible.

✅ The guard

tests/unit/project/collection_test.sh — itself nested, so the old glob wouldn't have collected it. Three assertions:

every test file on disk reaches make test
no fixture does
fixtures that would be swept in still exist — so assertion 2 can't pass vacuously

Both failure modes mutation-verified: reverting to the one-level glob reddens the first, dropping the fixtures/ exclusion reddens the second.

✅ Verification

Suite total 1626 → 1629 — exactly the three new tests, nothing lost.

(make test reports a different total from ./bashunit tests/ for pre-existing mode-dependent skips, not collection differences — which is why the guard compares file lists rather than totals.)

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

Prerequisite for #957. src/ is seventeen modules with no loose files; tests/unit is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs `make test` to find nested tests first. The Makefile collected with $(wildcard tests/*/*[tT]est.sh), which matches exactly one level. `./bashunit tests/` already recurses, so a nested test would have been run by three of the four CI matrix entries and silently skipped by `make test` -- green, and quietly testing less. Recursive collection alone is not the fix. A naive recursive glob also picks up four files under fixtures/ that are inputs to other tests rather than tests: tests/acceptance/fixtures/tests_path/{a,other}_test.sh tests/unit/fixtures/tests/example{1,2}_test.sh so fixtures/ is excluded by path. Collection is unchanged today: the same 156 files, byte for byte, verified against the old glob's output. tests/unit/project/collection_test.sh keeps it honest, and is itself nested -- the old glob would not have collected it. It asserts that every test file on disk reaches `make test`, that no fixture does, and that fixtures which would be swept in still exist, so the second assertion cannot pass vacuously. Both failure modes were verified by mutation: reverting to the one-level glob reddens the first test, dropping the fixtures exclusion reddens the second. The suite total goes 1626 -> 1629, which is exactly the three new tests.

Run from inside `make test`, the sub-make in collection_from_make inherits MAKEFLAGS and wraps its output in `make[1]: Entering/Leaving directory`. The positional `tail -n +2` stripped the Entering line instead of the header, so the comparison saw both the header and the trailing Leaving line and failed on the four make-driven CI jobs while every `./bashunit tests/` job passed. Filter on a `tests/` prefix instead of stripping a fixed number of lines, and clear MAKEFLAGS so the sub-make cannot inherit -j or a parent goal. Reproduced locally by running the guard through a wrapper Makefile, which fails before this change and passes after.

Chemaclass · 2026-08-01T18:02:51Z

🤔 Background

Related #957 — prerequisite for every PR in that issue.

src/ is 17 modules with no loose files. tests/unit/ is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs make test to find nested tests first.

⚠️ The problem this prevents

Makefile:67 collected with $(wildcard tests/*/*[tT]est.sh) — exactly one level. ./bashunit tests/ already recurses (verified). So the moment a test is nested, three of the four CI matrix entries would run it and make test would silently skip it — green, and quietly testing less.

💡 Why "just make it recursive" is wrong

A naive recursive glob also collects four files under fixtures/ that are inputs to other tests, not tests:

tests/acceptance/fixtures/tests_path/{a,other}_test.sh
tests/unit/fixtures/tests/example{1,2}_test.sh

So fixtures/ is excluded by path. Collection is unchanged today — the same 156 files, verified byte-for-byte against the old glob's output. This PR moves nothing; it only makes nesting possible.

✅ The guard

tests/unit/project/collection_test.sh — itself nested, so the old glob wouldn't have collected it. Three assertions:

every test file on disk reaches make test
no fixture does
fixtures that would be swept in still exist — so assertion 2 can't pass vacuously

Both failure modes mutation-verified: reverting to the one-level glob reddens the first, dropping the fixtures/ exclusion reddens the second.

✅ Verification

Suite total 1626 → 1629 — exactly the three new tests, nothing lost.

(make test reports a different total from ./bashunit tests/ for pre-existing mode-dependent skips, not collection differences — which is why the guard compares file lists rather than totals.)

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

Prerequisite for #957. src/ is seventeen modules with no loose files; tests/unit is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs `make test` to find nested tests first. The Makefile collected with $(wildcard tests/*/*[tT]est.sh), which matches exactly one level. `./bashunit tests/` already recurses, so a nested test would have been run by three of the four CI matrix entries and silently skipped by `make test` -- green, and quietly testing less. Recursive collection alone is not the fix. A naive recursive glob also picks up four files under fixtures/ that are inputs to other tests rather than tests: tests/acceptance/fixtures/tests_path/{a,other}_test.sh tests/unit/fixtures/tests/example{1,2}_test.sh so fixtures/ is excluded by path. Collection is unchanged today: the same 156 files, byte for byte, verified against the old glob's output. tests/unit/project/collection_test.sh keeps it honest, and is itself nested -- the old glob would not have collected it. It asserts that every test file on disk reaches `make test`, that no fixture does, and that fixtures which would be swept in still exist, so the second assertion cannot pass vacuously. Both failure modes were verified by mutation: reverting to the one-level glob reddens the first test, dropping the fixtures exclusion reddens the second. The suite total goes 1626 -> 1629, which is exactly the three new tests.

Run from inside `make test`, the sub-make in collection_from_make inherits MAKEFLAGS and wraps its output in `make[1]: Entering/Leaving directory`. The positional `tail -n +2` stripped the Entering line instead of the header, so the comparison saw both the header and the trailing Leaving line and failed on the four make-driven CI jobs while every `./bashunit tests/` job passed. Filter on a `tests/` prefix instead of stripping a fixed number of lines, and clear MAKEFLAGS so the sub-make cannot inherit -j or a parent goal. Reproduced locally by running the guard through a wrapper Makefile, which fails before this change and passes after.

Chemaclass · 2026-08-01T18:02:51Z

🤔 Background

Related #957 — prerequisite for every PR in that issue.

src/ is 17 modules with no loose files. tests/unit/ is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs make test to find nested tests first.

⚠️ The problem this prevents

Makefile:67 collected with $(wildcard tests/*/*[tT]est.sh) — exactly one level. ./bashunit tests/ already recurses (verified). So the moment a test is nested, three of the four CI matrix entries would run it and make test would silently skip it — green, and quietly testing less.

💡 Why "just make it recursive" is wrong

A naive recursive glob also collects four files under fixtures/ that are inputs to other tests, not tests:

tests/acceptance/fixtures/tests_path/{a,other}_test.sh
tests/unit/fixtures/tests/example{1,2}_test.sh

So fixtures/ is excluded by path. Collection is unchanged today — the same 156 files, verified byte-for-byte against the old glob's output. This PR moves nothing; it only makes nesting possible.

✅ The guard

tests/unit/project/collection_test.sh — itself nested, so the old glob wouldn't have collected it. Three assertions:

every test file on disk reaches make test
no fixture does
fixtures that would be swept in still exist — so assertion 2 can't pass vacuously

Both failure modes mutation-verified: reverting to the one-level glob reddens the first, dropping the fixtures/ exclusion reddens the second.

✅ Verification

Suite total 1626 → 1629 — exactly the three new tests, nothing lost.

(make test reports a different total from ./bashunit tests/ for pre-existing mode-dependent skips, not collection differences — which is why the guard compares file lists rather than totals.)

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

Prerequisite for #957. src/ is seventeen modules with no loose files; tests/unit is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs `make test` to find nested tests first. The Makefile collected with $(wildcard tests/*/*[tT]est.sh), which matches exactly one level. `./bashunit tests/` already recurses, so a nested test would have been run by three of the four CI matrix entries and silently skipped by `make test` -- green, and quietly testing less. Recursive collection alone is not the fix. A naive recursive glob also picks up four files under fixtures/ that are inputs to other tests rather than tests: tests/acceptance/fixtures/tests_path/{a,other}_test.sh tests/unit/fixtures/tests/example{1,2}_test.sh so fixtures/ is excluded by path. Collection is unchanged today: the same 156 files, byte for byte, verified against the old glob's output. tests/unit/project/collection_test.sh keeps it honest, and is itself nested -- the old glob would not have collected it. It asserts that every test file on disk reaches `make test`, that no fixture does, and that fixtures which would be swept in still exist, so the second assertion cannot pass vacuously. Both failure modes were verified by mutation: reverting to the one-level glob reddens the first test, dropping the fixtures exclusion reddens the second. The suite total goes 1626 -> 1629, which is exactly the three new tests.

Run from inside `make test`, the sub-make in collection_from_make inherits MAKEFLAGS and wraps its output in `make[1]: Entering/Leaving directory`. The positional `tail -n +2` stripped the Entering line instead of the header, so the comparison saw both the header and the trailing Leaving line and failed on the four make-driven CI jobs while every `./bashunit tests/` job passed. Filter on a `tests/` prefix instead of stripping a fixed number of lines, and clear MAKEFLAGS so the sub-make cannot inherit -j or a parent goal. Reproduced locally by running the guard through a wrapper Makefile, which fails before this change and passes after.

Chemaclass · 2026-08-01T18:02:51Z

🤔 Background

Related #957 — prerequisite for every PR in that issue.

src/ is 17 modules with no loose files. tests/unit/ is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs make test to find nested tests first.

⚠️ The problem this prevents

Makefile:67 collected with $(wildcard tests/*/*[tT]est.sh) — exactly one level. ./bashunit tests/ already recurses (verified). So the moment a test is nested, three of the four CI matrix entries would run it and make test would silently skip it — green, and quietly testing less.

💡 Why "just make it recursive" is wrong

A naive recursive glob also collects four files under fixtures/ that are inputs to other tests, not tests:

tests/acceptance/fixtures/tests_path/{a,other}_test.sh
tests/unit/fixtures/tests/example{1,2}_test.sh

So fixtures/ is excluded by path. Collection is unchanged today — the same 156 files, verified byte-for-byte against the old glob's output. This PR moves nothing; it only makes nesting possible.

✅ The guard

tests/unit/project/collection_test.sh — itself nested, so the old glob wouldn't have collected it. Three assertions:

every test file on disk reaches make test
no fixture does
fixtures that would be swept in still exist — so assertion 2 can't pass vacuously

Both failure modes mutation-verified: reverting to the one-level glob reddens the first, dropping the fixtures/ exclusion reddens the second.

✅ Verification

Suite total 1626 → 1629 — exactly the three new tests, nothing lost.

(make test reports a different total from ./bashunit tests/ for pre-existing mode-dependent skips, not collection differences — which is why the guard compares file lists rather than totals.)

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

Prerequisite for #957. src/ is seventeen modules with no loose files; tests/unit is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs `make test` to find nested tests first. The Makefile collected with $(wildcard tests/*/*[tT]est.sh), which matches exactly one level. `./bashunit tests/` already recurses, so a nested test would have been run by three of the four CI matrix entries and silently skipped by `make test` -- green, and quietly testing less. Recursive collection alone is not the fix. A naive recursive glob also picks up four files under fixtures/ that are inputs to other tests rather than tests: tests/acceptance/fixtures/tests_path/{a,other}_test.sh tests/unit/fixtures/tests/example{1,2}_test.sh so fixtures/ is excluded by path. Collection is unchanged today: the same 156 files, byte for byte, verified against the old glob's output. tests/unit/project/collection_test.sh keeps it honest, and is itself nested -- the old glob would not have collected it. It asserts that every test file on disk reaches `make test`, that no fixture does, and that fixtures which would be swept in still exist, so the second assertion cannot pass vacuously. Both failure modes were verified by mutation: reverting to the one-level glob reddens the first test, dropping the fixtures exclusion reddens the second. The suite total goes 1626 -> 1629, which is exactly the three new tests.

Run from inside `make test`, the sub-make in collection_from_make inherits MAKEFLAGS and wraps its output in `make[1]: Entering/Leaving directory`. The positional `tail -n +2` stripped the Entering line instead of the header, so the comparison saw both the header and the trailing Leaving line and failed on the four make-driven CI jobs while every `./bashunit tests/` job passed. Filter on a `tests/` prefix instead of stripping a fixed number of lines, and clear MAKEFLAGS so the sub-make cannot inherit -j or a parent goal. Reproduced locally by running the guard through a wrapper Makefile, which fails before this change and passes after.

Chemaclass · 2026-08-01T18:02:51Z

🤔 Background

Related #957 — prerequisite for every PR in that issue.

src/ is 17 modules with no loose files. tests/unit/ is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs make test to find nested tests first.

⚠️ The problem this prevents

Makefile:67 collected with $(wildcard tests/*/*[tT]est.sh) — exactly one level. ./bashunit tests/ already recurses (verified). So the moment a test is nested, three of the four CI matrix entries would run it and make test would silently skip it — green, and quietly testing less.

💡 Why "just make it recursive" is wrong

A naive recursive glob also collects four files under fixtures/ that are inputs to other tests, not tests:

tests/acceptance/fixtures/tests_path/{a,other}_test.sh
tests/unit/fixtures/tests/example{1,2}_test.sh

So fixtures/ is excluded by path. Collection is unchanged today — the same 156 files, verified byte-for-byte against the old glob's output. This PR moves nothing; it only makes nesting possible.

✅ The guard

tests/unit/project/collection_test.sh — itself nested, so the old glob wouldn't have collected it. Three assertions:

every test file on disk reaches make test
no fixture does
fixtures that would be swept in still exist — so assertion 2 can't pass vacuously

Both failure modes mutation-verified: reverting to the one-level glob reddens the first, dropping the fixtures/ exclusion reddens the second.

✅ Verification

Suite total 1626 → 1629 — exactly the three new tests, nothing lost.

(make test reports a different total from ./bashunit tests/ for pre-existing mode-dependent skips, not collection differences — which is why the guard compares file lists rather than totals.)

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

Prerequisite for #957. src/ is seventeen modules with no loose files; tests/unit is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs `make test` to find nested tests first. The Makefile collected with $(wildcard tests/*/*[tT]est.sh), which matches exactly one level. `./bashunit tests/` already recurses, so a nested test would have been run by three of the four CI matrix entries and silently skipped by `make test` -- green, and quietly testing less. Recursive collection alone is not the fix. A naive recursive glob also picks up four files under fixtures/ that are inputs to other tests rather than tests: tests/acceptance/fixtures/tests_path/{a,other}_test.sh tests/unit/fixtures/tests/example{1,2}_test.sh so fixtures/ is excluded by path. Collection is unchanged today: the same 156 files, byte for byte, verified against the old glob's output. tests/unit/project/collection_test.sh keeps it honest, and is itself nested -- the old glob would not have collected it. It asserts that every test file on disk reaches `make test`, that no fixture does, and that fixtures which would be swept in still exist, so the second assertion cannot pass vacuously. Both failure modes were verified by mutation: reverting to the one-level glob reddens the first test, dropping the fixtures exclusion reddens the second. The suite total goes 1626 -> 1629, which is exactly the three new tests.

Run from inside `make test`, the sub-make in collection_from_make inherits MAKEFLAGS and wraps its output in `make[1]: Entering/Leaving directory`. The positional `tail -n +2` stripped the Entering line instead of the header, so the comparison saw both the header and the trailing Leaving line and failed on the four make-driven CI jobs while every `./bashunit tests/` job passed. Filter on a `tests/` prefix instead of stripping a fixed number of lines, and clear MAKEFLAGS so the sub-make cannot inherit -j or a parent goal. Reproduced locally by running the guard through a wrapper Makefile, which fails before this change and passes after.

Chemaclass · 2026-08-01T18:02:51Z

🤔 Background

Related #957 — prerequisite for every PR in that issue.

src/ is 17 modules with no loose files. tests/unit/ is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs make test to find nested tests first.

⚠️ The problem this prevents

Makefile:67 collected with $(wildcard tests/*/*[tT]est.sh) — exactly one level. ./bashunit tests/ already recurses (verified). So the moment a test is nested, three of the four CI matrix entries would run it and make test would silently skip it — green, and quietly testing less.

💡 Why "just make it recursive" is wrong

A naive recursive glob also collects four files under fixtures/ that are inputs to other tests, not tests:

tests/acceptance/fixtures/tests_path/{a,other}_test.sh
tests/unit/fixtures/tests/example{1,2}_test.sh

So fixtures/ is excluded by path. Collection is unchanged today — the same 156 files, verified byte-for-byte against the old glob's output. This PR moves nothing; it only makes nesting possible.

✅ The guard

tests/unit/project/collection_test.sh — itself nested, so the old glob wouldn't have collected it. Three assertions:

every test file on disk reaches make test
no fixture does
fixtures that would be swept in still exist — so assertion 2 can't pass vacuously

Both failure modes mutation-verified: reverting to the one-level glob reddens the first, dropping the fixtures/ exclusion reddens the second.

✅ Verification

Suite total 1626 → 1629 — exactly the three new tests, nothing lost.

(make test reports a different total from ./bashunit tests/ for pre-existing mode-dependent skips, not collection differences — which is why the guard compares file lists rather than totals.)

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

Prerequisite for #957. src/ is seventeen modules with no loose files; tests/unit is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs `make test` to find nested tests first. The Makefile collected with $(wildcard tests/*/*[tT]est.sh), which matches exactly one level. `./bashunit tests/` already recurses, so a nested test would have been run by three of the four CI matrix entries and silently skipped by `make test` -- green, and quietly testing less. Recursive collection alone is not the fix. A naive recursive glob also picks up four files under fixtures/ that are inputs to other tests rather than tests: tests/acceptance/fixtures/tests_path/{a,other}_test.sh tests/unit/fixtures/tests/example{1,2}_test.sh so fixtures/ is excluded by path. Collection is unchanged today: the same 156 files, byte for byte, verified against the old glob's output. tests/unit/project/collection_test.sh keeps it honest, and is itself nested -- the old glob would not have collected it. It asserts that every test file on disk reaches `make test`, that no fixture does, and that fixtures which would be swept in still exist, so the second assertion cannot pass vacuously. Both failure modes were verified by mutation: reverting to the one-level glob reddens the first test, dropping the fixtures exclusion reddens the second. The suite total goes 1626 -> 1629, which is exactly the three new tests.

Run from inside `make test`, the sub-make in collection_from_make inherits MAKEFLAGS and wraps its output in `make[1]: Entering/Leaving directory`. The positional `tail -n +2` stripped the Entering line instead of the header, so the comparison saw both the header and the trailing Leaving line and failed on the four make-driven CI jobs while every `./bashunit tests/` job passed. Filter on a `tests/` prefix instead of stripping a fixed number of lines, and clear MAKEFLAGS so the sub-make cannot inherit -j or a parent goal. Reproduced locally by running the guard through a wrapper Makefile, which fails before this change and passes after.

Chemaclass · 2026-08-01T18:02:51Z

🤔 Background

Related #957 — prerequisite for every PR in that issue.

src/ is 17 modules with no loose files. tests/unit/ is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs make test to find nested tests first.

⚠️ The problem this prevents

Makefile:67 collected with $(wildcard tests/*/*[tT]est.sh) — exactly one level. ./bashunit tests/ already recurses (verified). So the moment a test is nested, three of the four CI matrix entries would run it and make test would silently skip it — green, and quietly testing less.

💡 Why "just make it recursive" is wrong

A naive recursive glob also collects four files under fixtures/ that are inputs to other tests, not tests:

tests/acceptance/fixtures/tests_path/{a,other}_test.sh
tests/unit/fixtures/tests/example{1,2}_test.sh

So fixtures/ is excluded by path. Collection is unchanged today — the same 156 files, verified byte-for-byte against the old glob's output. This PR moves nothing; it only makes nesting possible.

✅ The guard

tests/unit/project/collection_test.sh — itself nested, so the old glob wouldn't have collected it. Three assertions:

every test file on disk reaches make test
no fixture does
fixtures that would be swept in still exist — so assertion 2 can't pass vacuously

Both failure modes mutation-verified: reverting to the one-level glob reddens the first, dropping the fixtures/ exclusion reddens the second.

✅ Verification

Suite total 1626 → 1629 — exactly the three new tests, nothing lost.

(make test reports a different total from ./bashunit tests/ for pre-existing mode-dependent skips, not collection differences — which is why the guard compares file lists rather than totals.)

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

Prerequisite for #957. src/ is seventeen modules with no loose files; tests/unit is still 71 flat files with the module encoded in a filename prefix. Mirroring the layout needs `make test` to find nested tests first. The Makefile collected with $(wildcard tests/*/*[tT]est.sh), which matches exactly one level. `./bashunit tests/` already recurses, so a nested test would have been run by three of the four CI matrix entries and silently skipped by `make test` -- green, and quietly testing less. Recursive collection alone is not the fix. A naive recursive glob also picks up four files under fixtures/ that are inputs to other tests rather than tests: tests/acceptance/fixtures/tests_path/{a,other}_test.sh tests/unit/fixtures/tests/example{1,2}_test.sh so fixtures/ is excluded by path. Collection is unchanged today: the same 156 files, byte for byte, verified against the old glob's output. tests/unit/project/collection_test.sh keeps it honest, and is itself nested -- the old glob would not have collected it. It asserts that every test file on disk reaches `make test`, that no fixture does, and that fixtures which would be swept in still exist, so the second assertion cannot pass vacuously. Both failure modes were verified by mutation: reverting to the one-level glob reddens the first test, dropping the fixtures exclusion reddens the second. The suite total goes 1626 -> 1629, which is exactly the three new tests.

Run from inside `make test`, the sub-make in collection_from_make inherits MAKEFLAGS and wraps its output in `make[1]: Entering/Leaving directory`. The positional `tail -n +2` stripped the Entering line instead of the header, so the comparison saw both the header and the trailing Leaving line and failed on the four make-driven CI jobs while every `./bashunit tests/` job passed. Filter on a `tests/` prefix instead of stripping a fixed number of lines, and clear MAKEFLAGS so the sub-make cannot inherit -j or a parent goal. Reproduced locally by running the guard through a wrapper Makefile, which fails before this change and passes after.

Chemaclass added the refactoring Refactoring or cleaning related label Aug 1, 2026

Chemaclass self-assigned this Aug 1, 2026

Chemaclass merged commit 0bfaca7 into mainAug 1, 2026
37 checks passed

Chemaclass deleted the refactor/957-recursive-test-collection branch August 1, 2026 18:22

This was referenced Aug 1, 2026
refactor(tests): mirror the src/ module layout in tests/unit/ #957
Closed
refactor(tests): mirror the src/ module layout in tests/unit/ #960
Merged

Chemaclass added the refactoring Refactoring or cleaning related label Aug 1, 2026

Chemaclass self-assigned this Aug 1, 2026

Chemaclass merged commit 0bfaca7 into mainAug 1, 2026
37 checks passed

Chemaclass deleted the refactor/957-recursive-test-collection branch August 1, 2026 18:22

This was referenced Aug 1, 2026
refactor(tests): mirror the src/ module layout in tests/unit/ #957
Closed
refactor(tests): mirror the src/ module layout in tests/unit/ #960
Merged

Chemaclass added the refactoring Refactoring or cleaning related label Aug 1, 2026

Chemaclass self-assigned this Aug 1, 2026

Chemaclass merged commit 0bfaca7 into mainAug 1, 2026
37 checks passed

Chemaclass deleted the refactor/957-recursive-test-collection branch August 1, 2026 18:22

This was referenced Aug 1, 2026
refactor(tests): mirror the src/ module layout in tests/unit/ #957
Closed
refactor(tests): mirror the src/ module layout in tests/unit/ #960
Merged

Chemaclass added the refactoring Refactoring or cleaning related label Aug 1, 2026

Chemaclass self-assigned this Aug 1, 2026

Chemaclass merged commit 0bfaca7 into mainAug 1, 2026
37 checks passed

Chemaclass deleted the refactor/957-recursive-test-collection branch August 1, 2026 18:22

This was referenced Aug 1, 2026
refactor(tests): mirror the src/ module layout in tests/unit/ #957
Closed
refactor(tests): mirror the src/ module layout in tests/unit/ #960
Merged

Chemaclass added the refactoring Refactoring or cleaning related label Aug 1, 2026

Chemaclass self-assigned this Aug 1, 2026

Chemaclass merged commit 0bfaca7 into mainAug 1, 2026
37 checks passed

Chemaclass deleted the refactor/957-recursive-test-collection branch August 1, 2026 18:22

This was referenced Aug 1, 2026
refactor(tests): mirror the src/ module layout in tests/unit/ #957
Closed
refactor(tests): mirror the src/ module layout in tests/unit/ #960
Merged

Chemaclass added the refactoring Refactoring or cleaning related label Aug 1, 2026

Chemaclass self-assigned this Aug 1, 2026

Chemaclass merged commit 0bfaca7 into mainAug 1, 2026
37 checks passed

Chemaclass deleted the refactor/957-recursive-test-collection branch August 1, 2026 18:22

This was referenced Aug 1, 2026
refactor(tests): mirror the src/ module layout in tests/unit/ #957
Closed
refactor(tests): mirror the src/ module layout in tests/unit/ #960
Merged

Chemaclass added the refactoring Refactoring or cleaning related label Aug 1, 2026

Chemaclass self-assigned this Aug 1, 2026

Chemaclass merged commit 0bfaca7 into mainAug 1, 2026
37 checks passed

Chemaclass deleted the refactor/957-recursive-test-collection branch August 1, 2026 18:22

This was referenced Aug 1, 2026
refactor(tests): mirror the src/ module layout in tests/unit/ #957
Closed
refactor(tests): mirror the src/ module layout in tests/unit/ #960
Merged

Chemaclass added the refactoring Refactoring or cleaning related label Aug 1, 2026

Chemaclass self-assigned this Aug 1, 2026

Chemaclass merged commit 0bfaca7 into mainAug 1, 2026
37 checks passed

Chemaclass deleted the refactor/957-recursive-test-collection branch August 1, 2026 18:22

This was referenced Aug 1, 2026
refactor(tests): mirror the src/ module layout in tests/unit/ #957
Closed
refactor(tests): mirror the src/ module layout in tests/unit/ #960
Merged

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 1, 2026

🤔 Background

⚠️ The problem this prevents

💡 Why "just make it recursive" is wrong

✅ The guard

✅ Verification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 1, 2026

🤔 Background

⚠️ The problem this prevents

💡 Why "just make it recursive" is wrong

✅ The guard

✅ Verification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 1, 2026

🤔 Background

⚠️ The problem this prevents

💡 Why "just make it recursive" is wrong

✅ The guard

✅ Verification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 1, 2026

🤔 Background

⚠️ The problem this prevents

💡 Why "just make it recursive" is wrong

✅ The guard

✅ Verification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Uh oh!

Conversation

Chemaclass commented Aug 1, 2026