Skip to content

test(utils): migrate tests to ginkgo of pkg/utils/kubeclient/rbac_test.go#5579

Merged
TrafalgarZZZ merged 1 commit intofluid-cloudnative:masterfrom
adity1raut:kubeclient_5
Feb 25, 2026
Merged

test(utils): migrate tests to ginkgo of pkg/utils/kubeclient/rbac_test.go#5579
TrafalgarZZZ merged 1 commit intofluid-cloudnative:masterfrom
adity1raut:kubeclient_5

Conversation

@adity1raut
Copy link
Copy Markdown
Contributor

Ⅰ. Describe what this PR does

  • test(utils): migrate tests to ginkgo of pkg/utils/kubeclient/rbac_test.go

Ⅱ. Does this pull request fix one issue?

part of #5407

pkg/utils/kubeclient/rbac_test.go

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

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @adity1raut, 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 refactors several unit tests within the pkg/utils/kubeclient and pkg/webhook/plugins/requirenodewithfuse packages. The tests have been migrated from the standard Go testing package to the Ginkgo and Gomega testing frameworks, enhancing test structure, readability, and assertion capabilities for Kubernetes-related components. This migration improves the maintainability and expressiveness of the test suite.

Highlights

  • Test Framework Migration: Migrated existing unit tests in pkg/utils/kubeclient/rbac_test.go from the standard Go testing package to the Ginkgo and Gomega testing frameworks.
  • Test Framework Migration: Migrated existing unit tests in pkg/webhook/plugins/requirenodewithfuse/require_node_with_fuse_test.go to the Ginkgo and Gomega testing frameworks.
  • New Test Suite: Added a new Ginkgo test suite file (requirenodewithfuse_suite_test.go) to properly set up and run the Ginkgo tests for the requirenodewithfuse package.

🧠 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
Copy Markdown

fluid-e2e-bot Bot commented Jan 28, 2026

Hi @adity1raut. 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
Copy Markdown
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 tests in pkg/utils/kubeclient/rbac_test.go and pkg/webhook/plugins/requirenodewithfuse/require_node_with_fuse_test.go to use the Ginkgo testing framework. The changes are well-structured and follow Ginkgo conventions. I've added a couple of suggestions to further improve the tests. One suggestion is to make the deletion tests in rbac_test.go more robust by verifying that the resources are actually deleted. The other is to refactor a large test case in require_node_with_fuse_test.go into smaller, more focused tests for better readability and maintainability.

Comment on lines +63 to +64
err := DeleteServiceAccount(fakeClient, "test1", namespace)
Expect(err).NotTo(HaveOccurred())
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

This test only asserts that no error is returned. To be more thorough, it should also verify that the ServiceAccount is actually deleted. You can do this by attempting to Get the resource after deletion and expecting a NotFound error.

This same improvement can be applied to the tests for DeleteRole and DeleteRoleBinding.

You will need to add the following imports:

import (
    "context"
    apierrors "k8s.io/apimachinery/pkg/api/errors"
)
err := DeleteServiceAccount(fakeClient, "test1", namespace)
Expect(err).NotTo(HaveOccurred())

sa := &corev1.ServiceAccount{}
err = fakeClient.Get(context.TODO(), client.ObjectKey{Name: "test1", Namespace: namespace}, sa)
Expect(apierrors.IsNotFound(err)).To(BeTrue())

Comment on lines +78 to +95
It("should create plugin and mutate pod correctly", func() {
plugin, err := NewPlugin(cl, "")
Expect(err).NotTo(HaveOccurred())
Expect(plugin.GetName()).To(Equal(Name))

runtimeInfo, err := base.BuildRuntimeInfo("test", "fluid", "alluxio")
Expect(err).NotTo(HaveOccurred())

shouldStop, err := plugin.Mutate(pod, map[string]base.RuntimeInfoInterface{"pvcName": runtimeInfo})
Expect(err).NotTo(HaveOccurred())
Expect(shouldStop).To(BeFalse())

_, err = plugin.Mutate(pod, map[string]base.RuntimeInfoInterface{})
Expect(err).NotTo(HaveOccurred())

_, err = plugin.Mutate(pod, map[string]base.RuntimeInfoInterface{"pvcName": nil})
Expect(err).To(HaveOccurred())
})
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

This test case covers multiple scenarios (plugin creation, name check, and various mutation cases). It's a good practice in BDD-style testing to have one specific expectation per It block. Consider refactoring this into multiple, more focused It blocks. This improves readability and makes it easier to pinpoint failures.

You may need to add an import for github.com/fluid-cloudnative/fluid/pkg/webhook/plugins/api.

It("should create plugin and get name correctly", func() {
	plugin, err := NewPlugin(cl, "")
	Expect(err).NotTo(HaveOccurred())
	Expect(plugin.GetName()).To(Equal(Name))
})

Context("when mutating pod", func() {
	var plugin api.MutatingHandler
	BeforeEach(func() {
		var err error
		plugin, err = NewPlugin(cl, "")
		Expect(err).NotTo(HaveOccurred())
	})

	It("should not stop and not error with valid runtime info", func() {
		runtimeInfo, err := base.BuildRuntimeInfo("test", "fluid", "alluxio")
		Expect(err).NotTo(HaveOccurred())

		shouldStop, err := plugin.Mutate(pod, map[string]base.RuntimeInfoInterface{"pvcName": runtimeInfo})
		Expect(err).NotTo(HaveOccurred())
		Expect(shouldStop).To(BeFalse())
	})

	It("should not stop and not error with empty runtime info map", func() {
		_, err := plugin.Mutate(pod, map[string]base.RuntimeInfoInterface{})
		Expect(err).NotTo(HaveOccurred())
	})

	It("should error with nil runtime info", func() {
		_, err := plugin.Mutate(pod, map[string]base.RuntimeInfoInterface{"pvcName": nil})
		Expect(err).To(HaveOccurred())
	})
})

…t.go

Signed-off-by: adity1raut <araut7798@gmail.com>
@sonarqubecloud
Copy link
Copy Markdown

@codecov
Copy link
Copy Markdown

codecov Bot commented Jan 28, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.22%. Comparing base (e549f73) to head (0e6d1fe).
⚠️ Report is 97 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5579      +/-   ##
==========================================
+ Coverage   59.07%   59.22%   +0.15%     
==========================================
  Files         444      444              
  Lines       30431    30431              
==========================================
+ Hits        17978    18024      +46     
+ Misses      10947    10912      -35     
+ Partials     1506     1495      -11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
Member

@TrafalgarZZZ TrafalgarZZZ left a comment

Choose a reason for hiding this comment

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

/lgtm

@fluid-e2e-bot
Copy link
Copy Markdown

fluid-e2e-bot Bot commented Feb 25, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: TrafalgarZZZ

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

The pull request process is described 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

@TrafalgarZZZ TrafalgarZZZ merged commit 4d0b783 into fluid-cloudnative:master Feb 25, 2026
18 checks passed
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.

2 participants