test(fixtures): fail when a required fixture group is missing

[karagozemin]

Problem

The fixture-size checker reports a missing or empty configured fixture directory as SKIP and still exits successfully. Deleting an entire required fixture group can therefore bypass the size-budget CI check.

Task

Make configured fixture groups required. A missing or empty group must fail with a clear diagnostic. Add a focused regression test.

Acceptance criteria

• Missing and empty required groups produce a non-zero exit.
• Existing fixture groups still pass.
• The checker test suite covers the failure path.
• No fixture contents or budgets are changed.

Suggested implementation prompt

Update the fixture-size checker so a configured group cannot silently disappear, add a regression test using a temporary project fixture, run the checker tests, and keep the change scoped to this behavior.

[Iker2522]

I'd like to take this issue on!

I can fix the fixture-size checker so missing or empty configured fixture groups fail with a non-zero exit code and clear diagnostics instead of silently skipping.

I will add a focused regression test using a temporary project fixture to exercise both missing and empty failure paths, while ensuring existing fixture groups continue to pass and no budget thresholds are changed. PR ready in 1 day.

[leocagli]

I would like to work on this one.

I read scripts/check-fixture-sizes.mjs and its companion scripts/check-fixture-sizes.test.mjs. The gap is exactly as described: a configured group that resolves to a missing or empty directory takes the SKIP path and the process still exits 0, so deleting a whole fixture group silently disables the size budget it was meant to guard.

My plan, scoped to the behavior in the acceptance criteria:

• A configured group whose directory is absent, or present but with no matching files, becomes a hard failure with a diagnostic naming the group and the resolved path, so the message tells you which group vanished rather than just that something failed.
• Keep SKIP meaningful for the cases where it is legitimate, instead of removing it outright.
• Add the regression test against a temporary project fixture, covering both failure paths separately (absent directory and empty directory), since they fail for different reasons and a single test would let one of them regress unnoticed.
• No fixture contents and no budgets touched.

I maintain the Bitcoindefi and CosmosPay organizations, and I contribute from the Starmaker, Cosmos LATAM and Open Stellar communities.

[egekoca]

plase ser

[Hollujay]

I would like to work on this issue

[leocagli]

Can I work on it? PR is already open: #267

[grantfox-oss]

🦊 GrantFox — @egekoca has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #248)
2. Your PR will be reviewed by the Sub-Rosa-Issue maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@leocagli's PR #267 was approved and merged by @karagozemin.

🏆 @leocagli: You earned 40 FoxPoints for this contribution! Your current tier: Builder (1,684 total points). Track your full progress on GrantFox.

👏 Great work, @leocagli! Keep contributing to Sub-Rosa-Issue.