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
<100% test coverage for generated files #632
Comments
I took a look at some of the specific failures, and they all look spurious. I am, in principle, against lowering test coverage rate. It looks like the failures in The coverage failures in TL;DR: I don't think this coverage failure is indicative of anything serious. The instances just need to be worked around or new generated unit tests need to be added. |
Some of the recent fixes for other APIs have also removed this issue, or at least, I can't reproduce it when I generate the Spanner GAPIC locally using the most recent generator version. We can reopen the issue if it pops up again. |
I'm still seeing coverage failures in |
Looking in detail at the missing lines: none of the API invocation methods are being tested for the async clients: only the contructors / factories are being tested. None of the methods of the async pager are tested, either. |
I am having trouble recreating the issue as stated. Locally, I see a problem that seems to be related to mocking credentials:
How urgently is a fix needed? Is it just blocking regeneration? Are there any critical features that would be blocked if we deferred regeneration? |
@software-dov this issue is for unit test coverage, which we expect to be at 100% -- there should be no actual gRPC occurring. Looking at the |
Coverage is again / finally at 100% for googleapis/python-datastore#170. |
And we're back! |
Running
nox -s unit cover
gives the following coverage results:All the of files with <100% coverage are generated files. Should these files be at 100% coverage or should the
fail_under
parameter be lowered?Code can be found at: https://github.com/larkee/python-spanner/tree/generator-migration
The text was updated successfully, but these errors were encountered: