[wip] update coverage details to improve reporting

[derrickaw]

Please add a meaningful description for your change here

---

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

• Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
• Update CHANGES.md with noteworthy changes.
• If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

[gemini-code-assist]

Summary of Changes

Hello @derrickaw, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the Python test coverage reporting infrastructure by introducing support for parallel coverage collection and improving the post-test processing of coverage data. It configures the coverage tool to operate in parallel and modifies the test runner script to correctly combine these parallel results and generate XML reports when requested, thereby providing more comprehensive and flexible coverage insights.

Highlights

• Parallel Coverage Collection: The .coveragerc configuration has been updated to enable parallel coverage collection, allowing for more efficient coverage gathering in multi-process or multi-threaded test environments.
• Coverage Data Combination: The run_pytest.sh script now includes logic to automatically combine coverage data files using coverage combine when parallel coverage is enabled, ensuring a consolidated report.
• XML Coverage Report Generation: Conditional logic has been added to the run_pytest.sh script to generate an XML coverage report via coverage xml if the --cov-report=xml argument is passed to pytest.
• Script Exit Flow Improvement: The exit handling in run_pytest.sh has been refined to ensure the script completes its coverage operations before exiting, specifically removing an early exit condition.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• sdks/python/.coveragerc
  • Enabled parallel coverage collection by adding parallel = True under the [run] section.
• sdks/python/scripts/run_pytest.sh
  • Implemented logic to combine coverage data using coverage combine if parallel coverage is active in .coveragerc.
  • Added conditional generation of XML coverage reports using coverage xml when --cov-report=xml is specified.
  • Adjusted script exit conditions to ensure coverage operations complete before the script terminates.

Activity

• This pull request is marked as a work in progress ([wip]), indicating it may not be fully complete or ready for final review.
• The pull request description uses a generic template, suggesting no specific detailed intent or discussion has been provided by the author yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩