Add tests for coverage check and coverage --prefer-stubs#4251
Open
jorenham wants to merge 1 commit into
Open
Conversation
jorenham
added
the
coverage
|
According to mypy_primer, this change doesn't affect type check results on a corpus of open source code. ✅ |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
coverage checkcommand had no tests, and the prefer-stubs merging was only covered through test helpers that bypass the "real" pipeline.This adds tests for the
checkandreportCLI commands, plus two end-to-end--prefer-stubsruns: one for a.py+.pyiliving harmoneously together, and another for a stubs-only project where the.pyiand.pyhave a long-distance relation (.pylives in far away insite-package-path).Test Plan
No behavior changes; tests only (and they all pass 🎉)