-
Notifications
You must be signed in to change notification settings - Fork 213
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.
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
Branch coverage on continue
statement
#368
Comments
This is because of coverage.py bug nedbat/coveragepy#198, which is really a Python issue. There's nothing pytest-cov can do about it. |
7 tasks
AddahDraggon
added a commit
to wleklinskimateusz/aMAZEd
that referenced
this issue
Feb 7, 2025
AddahDraggon
added a commit
to wleklinskimateusz/aMAZEd
that referenced
this issue
Feb 10, 2025
* Added maze sizes and test for that * Added grid transformer class * Fixed reversing the original grid instead of a copy in __debug_print__ * Made maze.size() return 0,0 when empty and Grid react properly to it (aka not at all) * Added tests * Fixing test coverage bug from pytest-dev/pytest-cov#368 * Fixed MyPy complaining about not having proper type
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure if this is a feature or a bug, but the following snippet reports
3->5
as missing coverage ...... while the following code gives 100% branch test coverage
I realize the example above is a bit contrived, since there is nothing after the
continue
, but seems like the first snippet should have full test coverage?It seems there is something about the no-op statements, since the following also report missing coverage:
The text was updated successfully, but these errors were encountered: