This PR is to add comments to TestJindoEngine_DeleteFusePersistentVolume in pkg\ddc\jindo\delete_volume_test.go.#4626
Conversation
…\jindo\delete_volume_test.go. Signed-off-by: laiyindagm <a1269986600@163.com>
|
Hi @laiyindagm. 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 Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
|
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cheyang The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |



…\jindo\delete_volume_test.go.
Ⅰ. Describe what this PR does
to add comments to TestJindoEngine_DeleteFusePersistentVolume in pkg\ddc\jindo\delete_volume_test.go.
// TestJindoEngine_DeleteFusePersistentVolume tests the deletion of a Fuse Persistent Volume in the JindoEngine.
// It creates a fake client with a predefined Persistent Volume and initializes two instances of JindoEngine,
// one with runtime enabled and one without. It then runs test cases to verify the deletion behavior of the
// Persistent Volume in both scenarios.
//
// Test cases:
// - JindoEngine with runtime enabled: expects the Persistent Volume to be deleted without errors.
// - JindoEngine without runtime enabled: expects the Persistent Volume to be deleted with an error.
//
// The function uses the doTestCases helper to execute the test cases and validate the results.
Ⅱ. Does this pull request fix one issue?
fixes #4625