-
Notifications
You must be signed in to change notification settings - Fork 19
feat(ci): add unit tests #100
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
Conversation
Summary of ChangesHello @kevinlin09, 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 primarily focuses on enhancing the maintainability and quality of the test suite. It involves a significant restructuring of the test directory, moving existing tests from a 'legacy' folder to a 'unit' folder, alongside numerous code style and readability improvements. These changes aim to standardize the test codebase, address linting warnings, and improve the clarity of test assertions, ultimately contributing to a more robust and easier-to-manage testing environment. Highlights
🧠 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. Using Gemini Code AssistThe 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
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 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
|
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 primarily focuses on refactoring the test suite. Key changes include renaming test files from the legacy directory to unit, improving code formatting for better readability (e.g., breaking long lines), and adopting more Pythonic constructs like with statements for file handling and enumerate for loops. Several minor bugs in test helper functions were also fixed, and type checker warnings have been addressed by adding type: ignore comments.
The changes are generally positive and improve the quality of the test code. I've pointed out a few minor areas for improvement related to redundant type: ignore comments and an unnecessary pylint directive.
|
|
||
| def str2bool(str): | ||
| return True if str.lower() == "true" else False | ||
| def str2bool(test): # pylint: disable=redefined-builtin |
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.
The pylint: disable=redefined-builtin comment is no longer necessary and is misleading. It was applicable when the parameter was named str, which shadows a built-in. Since you've renamed the parameter to test (which is not a built-in), this disable directive can be removed.
| def str2bool(test): # pylint: disable=redefined-builtin | |
| def str2bool(test): |
| # type: ignore[index] | ||
| choices = msg_resp_obj["output"]["choices"] # type: ignore[index] |
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.
There seems to be a redundant type: ignore. The # type: ignore[index] on line 157 applies to the following line (158), but line 158 already has an inline # type: ignore[index]. You can remove the comment on line 157 to avoid this duplication.
| # type: ignore[index] | |
| choices = msg_resp_obj["output"]["choices"] # type: ignore[index] | |
| choices = msg_resp_obj["output"]["choices"] # type: ignore[index] |
| # type: ignore[index] | ||
| choices = msg_resp_obj["output"]["choices"] # type: ignore[index] |
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.
Similar to a previous comment, there is a redundant type: ignore here. The # type: ignore[index] on line 184 can be removed as line 185 already has an inline ignore.
| # type: ignore[index] | |
| choices = msg_resp_obj["output"]["choices"] # type: ignore[index] | |
| choices = msg_resp_obj["output"]["choices"] # type: ignore[index] |
| # type: ignore[index] | ||
| choices = msg_resp_obj["output"]["choices"] # type: ignore[index] |
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.
Description
[Describe what this PR does and why]
Related Issue: Fixes #[issue_number] or Relates to #[issue_number]
Security Considerations: [Check if API keys or sensitive credentials are exposed in code/logs]
Type of Change
Component(s) Affected
Checklist
Testing
[How to test these changes]
Additional Notes
[Optional: any other context]