Skip to content

test: guard fixture case groups#238

Merged
zeitlinger merged 3 commits intomainfrom
codex/case-group-registry-guard
Apr 27, 2026
Merged

test: guard fixture case groups#238
zeitlinger merged 3 commits intomainfrom
codex/case-group-registry-guard

Conversation

@zeitlinger
Copy link
Copy Markdown
Member

What changed

Add a registry-level test that validates the top-level tests/cases/* groups stay aligned with the built-in check names, with general as the only non-linter exception.

Why

The fixture harness groups cases by the first path segment under tests/cases. If a directory name drifts from the registered check name, the fixture layout silently stops matching the actual linter identity.

This adds a guardrail so names like ruff-format vs ruff-fmt are caught by tests instead of slipping into the case tree unnoticed.

Validation

  • cargo test test_case_groups_match_registered_checks
  • mise run lint:fix
  • mise run lint

Signed-off-by: Gregor Zeitlinger <[email protected]>
@zeitlinger zeitlinger changed the title [codex] test: guard fixture case groups tests: guard fixture case groups Apr 27, 2026
@zeitlinger zeitlinger marked this pull request as ready for review April 27, 2026 06:40
@zeitlinger zeitlinger requested a review from a team as a code owner April 27, 2026 06:40
Copilot AI review requested due to automatic review settings April 27, 2026 06:40
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a registry-level test to ensure tests/cases/* top-level fixture groups remain aligned with registered built-in check names (allowing general as the sole non-check group), preventing silent drift between fixture layout and linter identities.

Changes:

  • Introduce test_case_groups_match_registered_checks to validate tests/cases directory names against builtin() check names plus general.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread src/registry/tests.rs Outdated
@zeitlinger zeitlinger changed the title tests: guard fixture case groups test: guard fixture case groups Apr 27, 2026
zeitlinger and others added 2 commits April 27, 2026 08:56
Signed-off-by: Gregor Zeitlinger <[email protected]>
@zeitlinger zeitlinger merged commit 4fed595 into main Apr 27, 2026
13 checks passed
@zeitlinger zeitlinger deleted the codex/case-group-registry-guard branch April 27, 2026 09:50
This was referenced Apr 27, 2026
zeitlinger added a commit that referenced this pull request Apr 27, 2026
### Added

- add flint setup preflight migrations
([#233](#233))
- support managed linter configs and aqua-backed tool keys
([#228](#228))
- switch xmloxide to github backend
([#229](#229))
- add taplo formatter check
([#224](#224))
- *(init)* configure line length during init
([#218](#218))

### Fixed

- support renovate v43.136.3
([#223](#223))
- switch yaml-lint to ryl
([#226](#226))
- *(ruff)* install via github releases
([#227](#227))
- resolve init rollout regressions
([#220](#220))

### Other

- reduce fake-bin fixture coverage
([#240](#240))
- *(deps)* update dependency npm:renovate to v43.141.1
([#221](#221))
- guard fixture case groups
([#238](#238))
- *(deps)* update dependency grafana/flint to v0.20.4
([#235](#235))
- *(deps)* lock file maintenance
([#237](#237))
- *(deps)* update dependency mise to v2026.4.19
([#236](#236))
- *(deps)* update rust crate json5 to v1
([#232](#232))
- *(deps)* update taiki-e/install-action digest to 787505c
([#219](#219))
- *(deps)* update dependency grafana/flint to v0.20.3
([#225](#225))

> [!IMPORTANT]
> Close and reopen this PR to trigger CI checks.

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Gregor Zeitlinger <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants