Skip to content

test(common): migrate critical_fuse_pod_test.go to Ginkgo/Gomega#5643

Open
devsubid wants to merge 1 commit intofluid-cloudnative:masterfrom
devsubid:test/common-migrate-critical-fuse-pod-test-to-ginkgo
Open

test(common): migrate critical_fuse_pod_test.go to Ginkgo/Gomega#5643
devsubid wants to merge 1 commit intofluid-cloudnative:masterfrom
devsubid:test/common-migrate-critical-fuse-pod-test-to-ginkgo

Conversation

@devsubid
Copy link

Ⅰ. Describe what this PR does

Migrates pkg/common/critical_fuse_pod_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 TestCriticalFusePodEnabled and TestPortCheckEnabled to Ginkgo specs
  • 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
CriticalFusePodEnabled Verifies function returns false by default
PortCheckEnabled Verifies function returns false by default

Ⅳ. Describe how to verify it

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

Migrate pkg/common/critical_fuse_pod_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 TestCriticalFusePodEnabled and TestPortCheckEnabled to Ginkgo specs
- Use explicit ginkgo/gomega imports to avoid naming conflicts

Part of fluid-cloudnative#5407

Signed-off-by: SUBID DAS <itsmesubid@gmail.com>
@fluid-e2e-bot
Copy link

fluid-e2e-bot bot commented Jan 31, 2026

[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 trafalgarzzz for approval by writing /assign @trafalgarzzz 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:

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
Copy link
Contributor

Summary of Changes

Hello @devsubid, 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 modernizes the testing approach for specific utility functions within the pkg/common package. By transitioning from the standard Go testing package to Ginkgo v2 and Gomega, the tests now adopt a more expressive and readable BDD style, which can enhance maintainability and understanding of test specifications. This change primarily focuses on refactoring existing tests rather than introducing new functionality.

Highlights

  • Test Framework Migration: The pkg/common/critical_fuse_pod_test.go file has been migrated from the standard testing.T framework to Ginkgo v2 and Gomega for a Behavior-Driven Development (BDD) style of testing.
  • New Test Suite Setup: A new file, pkg/common/common_suite_test.go, has been introduced to set up the Ginkgo test suite for the common package, enabling the execution of Ginkgo specs.
  • Test Conversion: The existing TestCriticalFusePodEnabled and TestPortCheckEnabled functions have been converted into Ginkgo Describe and It blocks, utilizing Gomega matchers for assertions.
  • Explicit Imports: Explicit ginkgo. and gomega. imports are now used within the test files 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
Copy link

fluid-e2e-bot bot commented Jan 31, 2026

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 successfully migrates the tests in pkg/common/critical_fuse_pod_test.go to use Ginkgo and Gomega, improving the test structure with a BDD-style approach. The new suite setup in common_suite_test.go is correct. I've added one suggestion in critical_fuse_pod_test.go to use ginkgo.DescribeTable to reduce code duplication and make the tests more concise and easier to maintain for similar test cases.

Comment on lines +24 to +34
var _ = ginkgo.Describe("CriticalFusePodEnabled", func() {
ginkgo.It("should return false by default", func() {
gomega.Expect(CriticalFusePodEnabled()).To(gomega.BeFalse())
})
})

var _ = ginkgo.Describe("PortCheckEnabled", func() {
ginkgo.It("should return false by default", func() {
gomega.Expect(PortCheckEnabled()).To(gomega.BeFalse())
})
})
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For test cases that follow the same pattern, you can use ginkgo.DescribeTable to make the tests more concise and maintainable. This avoids duplicating the test logic for each function.

var _ = ginkgo.DescribeTable("Default boolean flags",
	func(f func() bool) {
		gomega.Expect(f()).To(gomega.BeFalse())
	},
	ginkgo.Entry("CriticalFusePodEnabled should be false by default", CriticalFusePodEnabled),
	ginkgo.Entry("PortCheckEnabled should be false by default", PortCheckEnabled),
)

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant