Proposal: adopt pytest-snap into pytest-dev

[cr5459]

Hi pytest-dev maintainers,

I’d like to propose adopting pytest-snapcheck into the pytest-dev organization.

---

Project links

• PyPI: https://pypi.org/project/pytest-snapcheck/
• GitHub Repo: https://github.com/cr5459/pytest-snap

---

Purpose

pytest-snapcheck is a plugin that takes a snapshot of every test run (outcomes, timings, nodeids) and lets you compare runs. This makes it easy to:

• Detect new or fixed failures between commits.
• Spot performance regressions with budgets (e.g. “fail if tests got 20% slower”).
• Produce deterministic JSON artifacts for CI systems to gate merges.

In short: it’s a guardrail for regressions — both correctness and performance — built directly into pytest.

---

Why it fits

• Follows the pytest plugin naming convention (pytest-*).
• Exposes a proper pytest11 entry point.
• Targets reproducibility, determinism, and CI use-cases (aligns with pytest philosophy of reliability).
• Small, composable design.

---

State

• Actively maintained and published on PyPI.
• CI on Linux/macOS (Python 3.9–3.12).
• tox.ini included for local/CI testing.
• Linting with ruff + mypy.
• Type hints with py.typed.
• README, CHANGELOG, LICENSE, and issue tracker all in place.

---

Bus factor

I’m the current maintainer and happy to add additional maintainers from pytest-dev.
The package is set up for Trusted Publishing so transfer of PyPI rights is straightforward.

---

Docs requirements

All requirements from the pytest-dev “Submitting Plugins” guide are met:

• Published on PyPI with pytest-* name.
• tox.ini with working envs.
• README, LICENSE, CHANGELOG.
• Issue tracker enabled.

---

If there are no objections and at least two approvals, I’d be happy to transfer the repo to pytest-dev and add the core maintainers as PyPI owners.

Thanks for considering!

— Cyril Rikh (pytest-snapcheck maintainer)

[bluetech]

Hi Cyril, the project looks good to me. There are only two points missing from the checklist:

• A tox.ini file
• A changelog file (unless you're planning to use github releases, should also be fine)

I don't think we are too strict about those, but if you add these it should be 100% bureaucracy compliant :)

[nicoddemus]

@cr5459 please transfer the ownership of the repository to @bluetech and he will take it from there. 👍

Also, please add some of the core members as owners in PyPI as well, please add me (nicoddemus) and @RonnyPfannschmidt (ronny).

[cr5459]

Thanks. I have sent the repo transfer request to @bluetech and added @nicoddemus and @RonnyPfannschmidt as PyPi owners.

[bluetech]

Transfer is complete, welcome to pytest-dev!

[cr5459]

thank you!