Split the `TestContext` into a dedicated `uv-test` crate
by zanieb
·
Feb 06, 2026 at 19:07 UTC
·
scan-7a0f5e5151f8b7d2
Get this automatically on every PR
Install the Axiomo GitHub App to get Signals as check runs and PR comments on every pull request.
Risk level: Critical (85%)
Split the TestContext into a dedicated uv-test crate
crates/uv-test/src/lib.rs contains TestContext code
Added uv-test to Cargo.toml and crates/uv/Cargo.toml
Test files modified but no evidence tests run
Trusted contributor with 1787 merged PRs. maintains 116 public repositories. has 908 followers. unfamiliar with crates/uv-test/src/lib.rs.
Review 18 high-priority file(s)
crates/uv-test/src/lib.rs
+223
223 lines changed; Source code
crates/uv/tests/it/edit.rs
+356
356 lines changed; Source code
crates/uv/tests/it/export.rs
+164
164 lines changed; Source code
crates/uv/tests/it/init.rs
+150
150 lines changed; Source code
crates/uv/tests/it/lock.rs
+589
589 lines changed; Source code
crates/uv/tests/it/pip_compile.rs
+756
756 lines changed; Source code
crates/uv/tests/it/pip_install.rs
+596
596 lines changed; Source code
crates/uv/tests/it/pip_install_scenarios.rs
+194
194 lines changed; Source code
crates/uv/tests/it/pip_sync.rs
+266
266 lines changed; Source code
crates/uv/tests/it/python_install.rs
+102
102 lines changed; Source code
+55 more files
240
minutes to review
extensive
effort level
none
staleness risk
Schedule dedicated review time; consider pair review
Critical risk level requires changes before approval
Consider breaking into smaller PRs
Why is security_scan_clean missing? Consider adding this check.
Why is coverage_maintained missing? Consider adding this check.