Skip to content

🧪 Unmeasure coverage in tests expected to fail #12531

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
webknjaz merged 2 commits into from
Jul 1, 2024
Merged

🧪 Unmeasure coverage in tests expected to fail #12531

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
634a83d
🧪 Unmeasure xfail tests
webknjaz Jun 25, 2024
f2acc65
📝 Add a change note for PR #12531
webknjaz Jun 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions .coveragerc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -29,3 +29,5 @@ exclude_lines =

^\s*if TYPE_CHECKING:
^\s*@overload( |$)

^\s*@pytest\.mark\.xfail
6 changes: 6 additions & 0 deletions changelog/12531.contrib.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
The coverage reporting configuration has been updated to exclude
pytest's own tests marked as expected to fail from the coverage
report. This has an effect of reducing the influence of flaky
tests on the resulting number.

-- by :user`webknjaz`

@webknjaz webknjaz Jul 2, 2024

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Syntax correction: #12560