test(common): migrate fluid_ufs_scheme_test.go to Ginkgo/Gomega

[devsubid]

Ⅰ. Describe what this PR does

Migrates pkg/common/fluid_ufs_scheme_test.go from testing.T to Ginkgo v2 and Gomega for BDD-style testing.

Changes:

• Add common_suite_test.go for Ginkgo test suite setup
• Convert IsFluidNativeScheme, IsFluidWebScheme, IsFluidRefSchema tests to DescribeTable/Entry
• Use explicit ginkgo./gomega. imports to avoid naming conflicts

Ⅱ. Does this pull request fix one issue?

Part of #5407

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.

No new test cases added. This PR migrates existing tests:

Test Case	Description
IsFluidNativeScheme	Tests pvc://, local://, http://, https:// schemes
IsFluidWebScheme	Tests http://, https:// vs other schemes
IsFluidRefSchema	Tests dataset:// scheme detection

Ⅳ. Describe how to verify it

go test ./pkg/common/... -v -count=1
# Expected: SUCCESS! -- 10 Passed | 0 Failed | 0 Pending | 0 Skipped

[fluid-e2e-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign yangyuliufeng for approval by writing /assign @yangyuliufeng in a comment. For more information see:The Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[gemini-code-assist]

Summary of Changes

Hello @devsubid, 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 focuses on modernizing the testing infrastructure within the pkg/common package. By transitioning from the traditional Go testing package to Ginkgo and Gomega, the aim is to improve the expressiveness, readability, and maintainability of the unit tests. This change introduces a more structured and behavior-driven approach to testing, making it easier to understand the intended behavior of the code at a glance.

Highlights

• Testing Framework Migration: The tests in pkg/common/fluid_ufs_scheme_test.go have been migrated from the standard testing.T framework to Ginkgo v2 and Gomega, adopting a Behavior-Driven Development (BDD) style.
• New Test Suite Setup: A new file, pkg/common/common_suite_test.go, has been added to set up the Ginkgo test suite for the common package, ensuring proper initialization for Ginkgo and Gomega.
• BDD-style Test Conversion: Existing test cases for IsFluidNativeScheme, IsFluidWebScheme, and IsFluidRefSchema have been converted to use Ginkgo's DescribeTable and Entry constructs, enhancing readability and structure.
• Explicit Imports: Explicit ginkgo. and gomega. imports are now used to prevent potential naming conflicts and improve code clarity.

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

[fluid-e2e-bot]

Hi @devsubid. Thanks for your PR.

I'm waiting for a fluid-cloudnative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[gemini-code-assist]

Code Review

This pull request successfully migrates the tests in fluid_ufs_scheme_test.go from the standard testing package to Ginkgo and Gomega. The changes are well-executed, following BDD principles and Ginkgo best practices. The new tests are more readable and descriptive, especially with the use of DescribeTable and meaningful Entry descriptions, which also fix some copy-paste errors in the old test case names. A new common_suite_test.go file is correctly added to set up the Ginkgo test suite. The code quality is high, and I have no further suggestions for improvement.