feat(ci): add github action unit_test

[kevinlin09]

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

• Bug fix
• New feature
• Breaking change
• Documentation
• Refactoring

Component(s) Affected

• Model
• Application
• Common
• Documentation
• Tests
• CI/CD

Checklist

• Pre-commit hooks pass
• Tests pass locally
• Documentation updated (if needed)
• Ready for review

Testing

[How to test these changes]

Additional Notes

[Optional: any other context]

[gemini-code-assist]

Summary of Changes

Hello @kevinlin09, 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 undertakes a significant refactoring of the project's test suite by reorganizing existing tests into tests/legacy/ and tests/unit/ directories. This foundational change is a prerequisite for integrating new unit testing workflows, likely via GitHub Actions, as indicated by the PR title. The update to pre-commit hooks ensures that code quality checks are applied appropriately to the new test structure, while numerous import paths and pylint directives have been adjusted to accommodate the new file organization.

Highlights

• Test Suite Refactoring: All existing test files and associated utilities have been moved from the root tests/ directory into a new tests/legacy/ subdirectory. This prepares the ground for a new test organization.
• New Unit Test Structure: A dedicated tests/unit/ directory has been created, and core testing components like base_test.py, constants.py, and mock_server.py have been relocated there, establishing a clear structure for new unit tests.
• Pre-commit Hook Updates: The .pre-commit-config.yaml file has been updated to modify the exclude patterns for various code quality hooks (e.g., black, flake8, pylint, eslint, prettier). These hooks now exclude the tests/legacy/ directory, ensuring that legacy tests are not subjected to the same strict checks as potentially new unit tests.
• Import Path Adjustments: Numerous import statements within the moved test files have been updated to reflect their new locations under tests/legacy/ or tests/unit/, maintaining correct module resolution.
• Pylint Directive Additions: Several pylint: disable comments have been added to various functions and variables across the moved test files, primarily for unused-argument, redefined-builtin, relative-beyond-top-level, protected-access, and consider-using-with to manage linting warnings in the refactored code.

🧠 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.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/unit_test.yml

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. ↩

[gemini-code-assist]

Code Review

This pull request primarily focuses on refactoring the test suite by restructuring the test directory and updating import paths accordingly. It also includes numerous code style improvements, such as modernizing string formatting to f-strings and addressing linting issues. Overall, these changes improve the codebase's structure and quality. I've identified a couple of areas in the test files related to file handling that could be improved to prevent potential resource leaks and ensure platform-independent behavior.

[gemini-code-assist]

Opening a file in text mode without specifying an encoding can lead to unexpected behavior on different platforms as it will use the system's default encoding. It's best practice to explicitly specify the encoding. You've disabled the unspecified-encoding pylint warning, but it's better to fix the underlying issue. If request_file.bin is a text file, please specify the encoding (e.g., encoding='utf-8'). If it's a binary file, it should be opened in binary mode ('rb').

Suggested change

	with open("tests/data/request_file.bin") as f:
	with open("tests/data/request_file.bin", encoding="utf-8") as f: