-
Notifications
You must be signed in to change notification settings - Fork 242
Reuse code for unit test execution rules #1564
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
Reuse code for unit test execution rules #1564
Conversation
Signed-off-by: Sergio Arroutbi <[email protected]>
Reviewer's GuideExtract and reuse the common pytest command by introducing a Makefile variable and updating test targets to use it, reducing duplication. Flow diagram for Makefile unit test command reuseflowchart TD
A[Define PYTEST_COMMON_CMD variable] --> B[unit-tests target uses PYTEST_COMMON_CMD]
A --> C[unit-tests-verbose target uses PYTEST_COMMON_CMD with extra flags]
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @sarroutbi - I've reviewed your changes and they look great!
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @sarroutbi, I'm Gemini Code Assist1! 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 focuses on improving the maintainability of the project's Makefile
by centralizing the command used for executing unit tests. By defining a common variable for the base pytest
command, it reduces duplication across different unit test targets, making future modifications to the test execution logic simpler and less error-prone.
Highlights
- Makefile Refactoring: I've introduced a new Makefile variable,
PYTEST_COMMON_CMD
, to encapsulate the base command for running unit tests. This centralizes the commonpytest
invocation. - Code Duplication Reduction: The
unit-tests
andunit-tests-verbose
targets in the Makefile now leverage the newly defined$(PYTEST_COMMON_CMD)
variable, eliminating redundant command definitions and making the Makefile more maintainable.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
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 issue 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 is currently in preview and 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 to provide feedback.
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
-
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. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request refactors the Makefile by introducing a PYTEST_COMMON_CMD
variable to consolidate common pytest
command invocations. This change enhances maintainability by reducing code duplication in the unit-tests
and unit-tests-verbose
targets. The implementation is straightforward and correctly preserves the existing behavior of these test targets. No issues of medium or higher severity were identified.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
LGTM |
Summary by Sourcery
Extract and reuse the common pytest command in Makefile test targets to remove duplication
Enhancements:
PYTEST_COMMON_CMD
)unit-tests
andunit-tests-verbose
targets to use the new variable