Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add functest coverage for MetadataBackupLabel #291

Merged
merged 1 commit into from
Dec 2, 2024

Conversation

alromeros
Copy link
Contributor

What this PR does / why we need it:

This PR adds a new functional test to cover the MetadataBackupLabel feature.

It also refactors some test helpers to avoid code repetition.

Release note:

NONE

@kubevirt-bot kubevirt-bot added dco-signoff: yes Indicates the PR's author has DCO signed all their commits. size/L labels Nov 6, 2024
@kubevirt-bot kubevirt-bot requested review from aglitke and awels November 6, 2024 10:25
Copy link
Contributor

@ShellyKa13 ShellyKa13 left a comment

Choose a reason for hiding this comment

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

looks good! small comment.
I think it will be cool if we will change the framework of creating a backup to be similar to how a vm is being created in kubevirt example: https://github.com/kubevirt/kubevirt/blob/main/tests/vm_test.go#L101
But this is a future thinking irrelevant to this PR :)

args := []string{
"create", "backup", backupName,
"--include-namespaces", namespace,
"--include-namespaces", includedNamespace,
Copy link
Contributor

@ShellyKa13 ShellyKa13 Nov 20, 2024

Choose a reason for hiding this comment

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

I see that currently the use of this function always provides includedNamespace but if you made it generic maybe you should treat it the same as the other variable with if includedNamespace != ""

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Nov 20, 2024
@kubevirt-bot
Copy link

Pull requests that are marked with lgtm should receive a review
from an approver within 1 week.

After that period the bot marks them with the label needs-approver-review.

/label needs-approver-review

@kubevirt-bot kubevirt-bot added the needs-approver-review Indicates that a PR requires a review from an approver. label Nov 27, 2024
@ShellyKa13
Copy link
Contributor

taking the liberty to also approve this to get this test change in
/approve

@kubevirt-bot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ShellyKa13

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

The pull request process is described here

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 2, 2024
@kubevirt-bot kubevirt-bot merged commit 8d5aefb into kubevirt:main Dec 2, 2024
5 checks passed
@kubevirt-bot
Copy link

/remove-label needs-approver-review

@kubevirt-bot kubevirt-bot removed the needs-approver-review Indicates that a PR requires a review from an approver. label Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. size/L
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants