Skip to content

Add dead-tests to Tools - #152

Open
dylanpulver wants to merge 1 commit into
cleder:mainfrom
dylanpulver:add-dead-tests
Open

dylanpulver wants to merge 1 commit into
cleder:mainfrom
dylanpulver:add-dead-tests

Conversation

@dylanpulver

@dylanpulver dylanpulver commented Nov 12, 2026 •

Copy link
Copy Markdown

Submission

  • Project: github.com/dylanpulver/dead-tests
  • PyPI: n/a (runs from a checkout with Python 3.12+, or as a Docker image)
  • License: MIT
  • Section: Tools

What it does and why it belongs here

It finds Python tests that can never fail: shadowed duplicate test names, functions pytest never collects, asserts that cannot run inside pytest.raises, and self-comparisons. I used it to find the uncollected tests and dead pytest.raises tails fixed in pydantic#13921, #14165 and #14201.

Checklist

  • It is a Python project or a resource about testing Python code.
  • It is open source under an OSI-approved license. It is not a commercial SaaS, a hosted platform, or a client for one.
  • It is maintained, documented, and used by people other than its author. (Maintained and documented, yes. It is new, so I cannot claim outside users yet.)
  • This pull request adds only one entry.
  • The entry is in alphabetical order within its section.
  • The entry has the format - [name](link) - Description., and the description is short and contains no marketing language.
  • I am the author or maintainer of this project: yes

Summary by Sourcery

New Features:

  • Add the dead-tests project to the Tools section of the curated Python testing resources list.

@semanticdiff-com

Copy link
Copy Markdown

Review changes with  SemanticDiff

@sourcery-ai

sourcery-ai Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

Documentation

Add dead-tests to the testing-tools list with a short description of the test failures it detects.

  • README.md L271

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Add dead-tests to the Tools list

📝 Documentation 🕐 Less than 5 minutes

Grey Divider

AI Description

• Add dead-tests to the alphabetized Tools section of the Python testing resources list.
• Describe its detection of uncollected tests and assertions that cannot run.
High-Level Assessment

A single alphabetized entry is the appropriate approach for this list. Before accepting it, verify the project's maturity against the contribution guidelines; the submission acknowledges it has no known users beyond its author.

Files changed (1) +1 / -0

Documentation (1) +1 / -0
README.mdList dead-tests in Tools +1/-0

List dead-tests in Tools

• Adds a link to dead-tests between csv-quality-gate and detect-test-pollution. The description identifies tests that never run or assertions that cannot execute.

README.md

@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Grey Divider

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Grey Divider

Tip of the day
💡 Did you know, you can open the rule or relationship behind a finding in one click

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@llamapreview llamapreview Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LlamaPReview — Verification needed

The linked project’s contents and ownership were not inspected, so its license, documentation, maintenance, capabilities, and the submitter’s role remain unverified; whether outside use is expected is also unknown.

Owner action: Inspect the project to verify its eligibility and the stated claims, and determine whether outside use is expected or an exception is acceptable.

Review details and evidence

Material unknowns

  • The linked project’s contents and ownership were not inspected, so its license, documentation, maintenance, capabilities, and the submitter’s role remain unverified; whether outside use is expected is also unknown. An ineligible or misdescribed resource would change the merge judgment. The author’s inability to claim outside users does not establish that there are none.

LlamaPReview checks

  • Reviewed changed regions in README.md.
  • Read the complete PR-head file README.md.

Still coding alone? Open CarbonChat, a chat room right inside Codex.

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