Skip to content

test(mountpropagationinjector): enhance unit tests for plugin #5572

Merged
fluid-e2e-bot[bot] merged 1 commit intofluid-cloudnative:masterfrom
adity1raut:mountpropagationinjector
Feb 25, 2026
Merged

test(mountpropagationinjector): enhance unit tests for plugin #5572
fluid-e2e-bot[bot] merged 1 commit intofluid-cloudnative:masterfrom
adity1raut:mountpropagationinjector

Conversation

@adity1raut
Copy link
Copy Markdown
Contributor

…nality

Ⅰ. Describe what this PR does

  • test(mountpropagationinjector): enhance unit tests for plugin

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

Ⅳ. Describe how to verify it

Ⅴ. Special notes for reviews

…nality

Signed-off-by: adity1raut <araut7798@gmail.com>
@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 significantly improves the testing infrastructure for the mountpropagationinjector plugin. By adopting the Ginkgo and Gomega frameworks, the tests are now more readable, maintainable, and comprehensive. The changes ensure that the plugin's core logic for mutating pods is thoroughly validated across different input conditions, enhancing the overall reliability of the webhook component.

Highlights

  • Test Framework Migration: The unit tests for the mountpropagationinjector plugin have been migrated from the standard testing package to use Ginkgo and Gomega, providing a more structured and behavior-driven testing approach.
  • Enhanced Test Coverage: New test cases have been added to cover various scenarios for the Mutate method, including successful plugin creation, mutation with valid runtime information, handling empty runtime information, and correctly identifying errors when runtimeInfo is nil.
  • New Test Suite: A dedicated test suite file (mountpropagationinjector_suite_test.go) was introduced to properly initialize the Ginkgo and Gomega testing frameworks for the 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.

@sonarqubecloud
Copy link
Copy Markdown

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 refactors the unit tests for the mountpropagationinjector plugin to use the Ginkgo and Gomega testing frameworks. The changes improve the structure and readability of the tests. I've found one area for improvement regarding variable scoping in the tests to make them more robust, which I've detailed in a specific comment. Otherwise, the refactoring is well done.

Comment on lines +49 to +58
BeforeEach(func() {
runtimeInfo, err = base.BuildRuntimeInfo("test", "fluid", "alluxio")
Expect(err).NotTo(HaveOccurred())
pod = &corev1.Pod{
ObjectMeta: metav1.ObjectMeta{
Name: "test",
Namespace: "test",
},
}
})
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

The err variable from the outer scope is being overwritten in this BeforeEach block. This can lead to confusing test failures. If NewPlugin in the outer BeforeEach were to fail, the error would be masked here, and subsequent tests would likely panic instead of failing with a clear message. It's better to use a local variable for the error from BuildRuntimeInfo and to check the error from the outer scope at the beginning of this block to ensure the plugin was created successfully.

        BeforeEach(func() {
            Expect(err).NotTo(HaveOccurred())
            var e error
            runtimeInfo, e = base.BuildRuntimeInfo("test", "fluid", "alluxio")
            Expect(e).NotTo(HaveOccurred())
            pod = &corev1.Pod{
                ObjectMeta: metav1.ObjectMeta{
                    Name:      "test",
                    Namespace: "test",
                },
            }
        })

@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.07%. Comparing base (e549f73) to head (a86b367).
⚠️ Report is 88 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #5572   +/-   ##
=======================================
  Coverage   59.07%   59.07%           
=======================================
  Files         444      444           
  Lines       30431    30431           
=======================================
  Hits        17978    17978           
  Misses      10947    10947           
  Partials     1506     1506           

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

@adity1raut
Copy link
Copy Markdown
Contributor Author

/cc @cheyang

@fluid-e2e-bot fluid-e2e-bot bot requested a review from cheyang February 23, 2026 05:14
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

@fluid-e2e-bot fluid-e2e-bot bot merged commit 299e8f8 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