ADORSYS-GIS / ADORSYS-GIS/lightbridge-governance

[Ticket]: Extract inline test modules into tests/

未关闭
#175 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
ticket
主要语言
Rust
星标
1
派生
2
平均合并
14 小时 36 分钟
30 天内合并 PR
107

描述

### Type

Technical debt

### Summary

Move large inline `#[cfg(test)]` modules into their own files. This is the cheapest, lowest-risk portion of the ratchet.

### Intent

Roughly 840 of `config.rs`'s 1351 lines are its precedence test module. Extracting tests reclaims a large share of the debt with near-zero behaviour risk — the right thing to do first.

### Source of truth (links)

- #162 (parent epic), #173 (the baseline that orders this work)

### Acceptance Criteria

1. Test modules extracted where extraction is clean.
2. Every test still runs — **assert the count did not drop**, do not eyeball it.
3. No test body changes.
4. Tests needing crate-private access are documented as staying inline, with the reason.

### Out of Scope

Behaviour changes of any kind. This is a pure refactor.

### Technical Context

Some tests legitimately need private access and must stay. Say which, and why, rather than making items public to move them.

### Risks

A silently dropped test file is invisible in a green run. Compare test counts before and after, explicitly.

### Test Plan

Test count before equals test count after. State both numbers in the PR.

贡献指南

打开贡献指南

调研方向

Start by inspecting config.rs and its inline #[cfg(test)] precedence module, then establish the existing test count before moving clean modules into tests/. Run the full test suite afterward and compare the counts explicitly; document any modules that remain inline because they require crate-private access, and state both counts when done.

由索引模型根据 Issue 内容生成。

评估

技术栈
rust
领域
testing
Issue 类型
重构
难度
3/5
预计耗时
1-2 天
活跃度
活跃
描述清晰度
基本清楚
新手友好度
72/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。