Skip to content

test: reduce registry manifest test repetition#2

Draft
PascalThuet wants to merge 2 commits into
chore/integration-test-isolationfrom
chore/parallelize-integration-tests
Draft

test: reduce registry manifest test repetition#2
PascalThuet wants to merge 2 commits into
chore/integration-test-isolationfrom
chore/parallelize-integration-tests

Conversation

@PascalThuet

Copy link
Copy Markdown
Owner

What

Reduce the expensive multi-install manifest contract from one CLI setup per safe-integration pair to two aggregate install orders: forward and reverse.

This keeps the pairwise manifest-disjoint assertion, but builds the manifests once per order instead of repeating the same setup for every pair.

Stack

Stacked on github#3144. Retarget this PR after github#3144 lands, or recreate it against upstream if needed.

Validation

  • uv sync --extra test
  • uvx ruff check tests/integrations/test_registry.py
  • git diff --check
  • .venv/bin/python -m pytest tests/integrations/test_registry.py --durations=30 -q (1035 passed in 34.86s)
  • .venv/bin/python -m pytest tests/integrations --durations=30 -q before the final naming/comment cleanup (2500 passed, 1 skipped in 236.69s)

Comparison on the same machine:

  • Base stack PR: tests/integrations/test_registry.py collected 1223 tests and took 248.55s
  • This PR: tests/integrations/test_registry.py collects 1035 tests and took 34.86s

Disclosure

Prepared by Codex (model: GPT-5) on behalf of @PascalThuet.

Assisted-by: Codex (model: GPT-5, autonomous)
Add a >=2 precondition, explain why two install orders are tested
(manifests are order-independent; the orders only vary the init path),
and build the manifest map with a comprehension.
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.

1 participant