Skip to content

Conversation

@devsubid
Copy link

Ⅰ. Describe what this PR does

Migrates pkg/common/hostpid_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 TestHostPIDEnabled table-driven test 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. This PR migrates existing tests:

Test Case Description
nil annotations Returns false
empty annotations Returns false
wrong value Returns false for invalid value
'true' value Returns true
'True' value Returns true (case-insensitive)

Ⅳ. Describe how to verify it

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

Migrate pkg/common/hostpid_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 TestHostPIDEnabled table-driven test to DescribeTable/Entry
- 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 updates the testing infrastructure within the pkg/common package by transitioning its unit tests from the standard Go testing package to the Ginkgo v2 and Gomega frameworks. This modernization effort aims to improve test readability, maintainability, and adherence to Behavior-Driven Development (BDD) principles, specifically by converting an existing table-driven test to the new framework's style.

Highlights

  • Test Framework Migration: Migrated pkg/common/hostpid_test.go from the standard testing.T package to Ginkgo v2 and Gomega for Behavior-Driven Development (BDD) style testing.
  • Ginkgo Suite Setup: Introduced a new file, common_suite_test.go, to properly set up and initialize the Ginkgo test suite for the common package.
  • Table-Driven Test Conversion: Refactored the existing TestHostPIDEnabled table-driven test into Ginkgo's DescribeTable and Entry format, enhancing readability and structure.
  • Explicit Imports: Ensured explicit ginkgo. and gomega. imports are used throughout the migrated test file to prevent potential naming conflicts and improve 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.

@sonarqubecloud
Copy link

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/hostpid_test.go to use the Ginkgo and Gomega testing frameworks, which is a good step towards adopting BDD-style testing. The new test suite setup is correct. I have provided one suggestion to further improve the idiomatic use of Ginkgo/Gomega by splitting the test table and using more specific matchers, which will enhance the readability and maintainability of the tests.

Comment on lines +24 to +38
var _ = ginkgo.Describe("HostPIDEnabled", func() {
ginkgo.DescribeTable("should correctly determine if HostPID is enabled",
func(annotations map[string]string, expected bool) {
gomega.Expect(HostPIDEnabled(annotations)).To(gomega.Equal(expected))
},
{
name: "not exist, return false",
args: args{
annotations: map[string]string{},
},
want: false,
},
{
name: "wrong value, return false",
args: args{
annotations: map[string]string{
RuntimeFuseHostPIDKey: "sss",
},
},
want: false,
},
{
name: "exist, return true",
args: args{
annotations: map[string]string{
RuntimeFuseHostPIDKey: "true",
},
},
want: true,
},
{
name: "exist True, return true",
args: args{
annotations: map[string]string{
RuntimeFuseHostPIDKey: "True",
},
},
want: true,
},
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
if got := HostPIDEnabled(tt.args.annotations); got != tt.want {
t.Errorf("HostPIDEnabled() = %v, want %v", got, tt.want)
}
})
}
}
ginkgo.Entry("nil annotations return false", nil, false),
ginkgo.Entry("empty annotations return false", map[string]string{}, false),
ginkgo.Entry("wrong value returns false",
map[string]string{RuntimeFuseHostPIDKey: "sss"}, false),
ginkgo.Entry("'true' returns true",
map[string]string{RuntimeFuseHostPIDKey: "true"}, true),
ginkgo.Entry("'True' returns true",
map[string]string{RuntimeFuseHostPIDKey: "True"}, true),
)
})
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

While the current implementation is correct, we can make it more idiomatic and readable by leveraging more of Ginkgo's BDD-style features.

I suggest splitting the DescribeTable into two separate tables: one for cases that should return true and another for cases that should return false. This makes the test's intent clearer.

Additionally, using the more specific gomega.BeTrue() and gomega.BeFalse() matchers is preferred over gomega.Equal(true) and gomega.Equal(false) for boolean assertions as it leads to more descriptive failure messages.

Suggested change
var _ = ginkgo.Describe("HostPIDEnabled", func() {
ginkgo.DescribeTable("should correctly determine if HostPID is enabled",
func(annotations map[string]string, expected bool) {
gomega.Expect(HostPIDEnabled(annotations)).To(gomega.Equal(expected))
},
{
name: "not exist, return false",
args: args{
annotations: map[string]string{},
},
want: false,
},
{
name: "wrong value, return false",
args: args{
annotations: map[string]string{
RuntimeFuseHostPIDKey: "sss",
},
},
want: false,
},
{
name: "exist, return true",
args: args{
annotations: map[string]string{
RuntimeFuseHostPIDKey: "true",
},
},
want: true,
},
{
name: "exist True, return true",
args: args{
annotations: map[string]string{
RuntimeFuseHostPIDKey: "True",
},
},
want: true,
},
}
for _, tt := range tests {
t.Run(tt.name, func(t *testing.T) {
if got := HostPIDEnabled(tt.args.annotations); got != tt.want {
t.Errorf("HostPIDEnabled() = %v, want %v", got, tt.want)
}
})
}
}
ginkgo.Entry("nil annotations return false", nil, false),
ginkgo.Entry("empty annotations return false", map[string]string{}, false),
ginkgo.Entry("wrong value returns false",
map[string]string{RuntimeFuseHostPIDKey: "sss"}, false),
ginkgo.Entry("'true' returns true",
map[string]string{RuntimeFuseHostPIDKey: "true"}, true),
ginkgo.Entry("'True' returns true",
map[string]string{RuntimeFuseHostPIDKey: "True"}, true),
)
})
var _ = ginkgo.Describe("HostPIDEnabled", func() {
ginkgo.DescribeTable("should return false when HostPID is not enabled",
func(annotations map[string]string) {
gomega.Expect(HostPIDEnabled(annotations)).To(gomega.BeFalse())
},
ginkgo.Entry("with nil annotations", nil),
ginkgo.Entry("with empty annotations", map[string]string{}),
ginkgo.Entry("with an invalid value", map[string]string{RuntimeFuseHostPIDKey: "sss"}),
)
ginkgo.DescribeTable("should return true when HostPID is enabled",
func(annotations map[string]string) {
gomega.Expect(HostPIDEnabled(annotations)).To(gomega.BeTrue())
},
ginkgo.Entry("with value 'true'", map[string]string{RuntimeFuseHostPIDKey: "true"}),
ginkgo.Entry("with value 'True' (case-insensitive)", map[string]string{RuntimeFuseHostPIDKey: "True"}),
)
})

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