Skip to content

fix(ci): classify the merged regression tests explicitly in the layout inventories - #5075

Merged
lidge-jun merged 1 commit into
devfrom
codex/5059-register-regression-tests
Sep 18, 2026
Merged

lidge-jun merged 1 commit into
devfrom
codex/5059-register-regression-tests

Conversation

@lidge-jun

@lidge-jun lidge-jun commented Sep 18, 2026

Copy link
Copy Markdown
Owner

Summary

The regression tests that landed with #5050, #5051 and #5055 are not in the authoritative
test-layout inventories. They run today only because the regex seeds in
scripts/test-layout/layout.json place a conventionally named file, which is exactly what the
seeds are for — carrying a brand-new file until someone classifies it. Nobody ever did, so three
merged regression tests have no recorded owner and nothing would notice if a rename or a move
quietly dropped them (#5059).

layout.explicit and tests/fixtures/test-layout-expected.json are two copies of one table and
the membership oracle already asserts they are identical, so both sides get the same three
entries:

File Domain Subject
tests/ci-workflows/ci-structure-gate.test.ts ci-workflows #5050
tests/responses/responses-code-mode-patch-compile.test.ts responses #5051
tests/gui/gui-codex-usage-score-parity.test.ts gui #5055

A test in tests/test-layout-tooling.test.ts names the three so they cannot fall out again
without failing, and checks that each one actually sits in the directory its registration
claims. A registration pointing at a path the tree does not have is a claim, not a fact.

What this deliberately does not do is introduce a repository-wide "every test must be explicit"
rule. That would change the existing seed policy for 1364 entries and is a separate decision;
this change fixes the three files the issue is about.

Closes #5059

Verification

No local suite was run; this repository verifies on hosted CI. The change is inventory data plus
one oracle test, and the existing guards bind it: membership oracle > the live tree and the fixture agree entry by entry compares layout.explicit against the fixture and fails on any
divergence, and tests/test-layout.test.ts fails if a registered file does not sit in its
domain. Both inventories were re-read after the edit and parse to identical maps of 1367 entries.

Checklist

  • Scope stays focused and avoids unrelated cleanup.
  • Docs or release notes were updated when needed.
  • Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

Summary by CodeRabbit

  • Tests
    • Expanded test-layout validation for regression tests across CI workflows, response handling, and GUI coverage.
    • Added checks confirming tests are explicitly assigned to the correct functional areas and located in the expected directories.
    • Updated layout expectations to keep test organization consistent and prevent future classification errors.

…t inventories

The regex seeds place a conventionally named file, so a regression test can sit in the tree, run in CI, and still be absent from the authoritative table. That is how the regression tests for #5050, #5051 and #5055 landed without ever entering scripts/test-layout/layout.json or tests/fixtures/test-layout-expected.json (#5059).

The two inventories are two copies of one table and the membership oracle already compares them, so both sides get the same three entries. A new test names the three files so they cannot fall out again silently, and checks that each one actually sits in the directory its registration claims.

No repository-wide explicit-registration policy is introduced here; the seeds keep carrying brand-new files as designed.
@lidge-jun
lidge-jun requested a review from Ingwannu as a code owner September 18, 2026 17:49
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 18, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-18T17:52:17.463570Z 7529de9 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@github-actions

Copy link
Copy Markdown
Contributor

Deterministic PR hygiene checks passed.

@github-actions github-actions Bot added the bug Something isn't working label Sep 18, 2026
@coderabbitai

coderabbitai Bot commented Sep 18, 2026

Copy link
Copy Markdown
Contributor

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 1e741038-157b-466f-a624-020922970bf3

📥 Commits

Reviewing files that changed from the base of the PR and between 6044a9a and 7529de9.

📒 Files selected for processing (3)
  • scripts/test-layout/layout.json
  • tests/fixtures/test-layout-expected.json
  • tests/test-layout-tooling.test.ts

Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review.


📝 Walkthrough

Walkthrough

The change adds explicit inventory entries for three regression tests, updates the expected layout fixture, and adds a membership-oracle regression test that verifies ownership and file placement.

Changes

Test layout inventory

Layer / File(s) Summary
Explicit registration and validation
scripts/test-layout/layout.json:1534-1537, tests/fixtures/test-layout-expected.json:1366-1369, tests/test-layout-tooling.test.ts:265-287
The layout and expected fixture explicitly map the CI, responses, and GUI regression tests to their owner domains. The membership-oracle test verifies these mappings and the corresponding tests/<domain>/<filename> paths. The existing Devin mapping remains under providers.

Priority: ➖ Normal

Estimated code review effort: 2 (Simple) | ~10 minutes

Change: Other · Severity of issue fixed: Medium

Merge Risk: ⚪ Minimal · up to 7529d

The inventory, fixture, and membership checks are aligned, so this change is ready to merge with normal checks.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: adding explicit layout classifications for the merged regression tests in CI, responses, and GUI inventories.
Linked Issues check ✅ Passed Issue #5059 requires three explicit registrations in both authoritative inventories, correct domains, fixture verification, and regression coverage. The PR summary records these entries: `ci-structure…
Out of Scope Changes check ✅ Passed The changed files are scripts/test-layout/layout.json, tests/fixtures/test-layout-expected.json, and tests/test-layout-tooling.test.ts. They update the maintained layout inventories and add regr…
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@lidge-jun
lidge-jun merged commit 3d5efc7 into dev Sep 18, 2026
31 checks passed
@lidge-jun
lidge-jun deleted the codex/5059-register-regression-tests branch September 18, 2026 18:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant