finding_id: REV-2026-011
priority: P1
area: maven-plugin
kind: test-gap
paths:
Summary
Add real Maven plugin consumer integration tests using temporary fixture projects and CI execution.
Evidence
Global review finding REV-2026-011 identified a hand-written test in main source with a hard-coded personal path and no real consumer-project coverage for generate, analyze, autoFix, force, missing-file, generated compilation, or CI execution.
Impact
Maven-plugin regressions can pass unit tests while failing for actual consumers, and local-only tests are not reproducible or enforced in CI.
Scope
Remove the hard-coded main-source manual test, use Maven Invoker or an equivalent temporary fixture project, cover all required goals and failure modes, compile generated sources, and wire the integration suite into CI.
Out of scope
Core generator behavior and document auto-fix implementation, which are tracked by the blocking issues.
Acceptance criteria
- 移除 main source 中硬编码个人路径的手工测试
- 使用 Maven Invoker 或等价临时 fixture project
- 真实覆盖 generate/analyze/autoFix/force/缺文件
- 验证生成源码可编译并在 CI 执行
Verification
Run the integration suite in a clean checkout and CI-like Maven environment; assert goal outcomes, missing-file behavior, force behavior, and compilation of generated sources.
Rollback
Revert the integration-test harness and CI wiring while retaining portable fixtures and documenting any Maven-environment assumptions.
Dependencies
Blocked by REV-2026-004 (#15) and REV-2026-005 (#5). Do not add automation:ready until both dependencies are completed and design review is complete.
finding_id: REV-2026-011
priority: P1
area: maven-plugin
kind: test-gap
paths:
blocked_by:
automation: needs-design
Summary
Add real Maven plugin consumer integration tests using temporary fixture projects and CI execution.
Evidence
Global review finding REV-2026-011 identified a hand-written test in main source with a hard-coded personal path and no real consumer-project coverage for generate, analyze, autoFix, force, missing-file, generated compilation, or CI execution.
Impact
Maven-plugin regressions can pass unit tests while failing for actual consumers, and local-only tests are not reproducible or enforced in CI.
Scope
Remove the hard-coded main-source manual test, use Maven Invoker or an equivalent temporary fixture project, cover all required goals and failure modes, compile generated sources, and wire the integration suite into CI.
Out of scope
Core generator behavior and document auto-fix implementation, which are tracked by the blocking issues.
Acceptance criteria
Verification
Run the integration suite in a clean checkout and CI-like Maven environment; assert goal outcomes, missing-file behavior, force behavior, and compilation of generated sources.
Rollback
Revert the integration-test harness and CI wiring while retaining portable fixtures and documenting any Maven-environment assumptions.
Dependencies
Blocked by REV-2026-004 (#15) and REV-2026-005 (#5). Do not add
automation:readyuntil both dependencies are completed and design review is complete.