Skip to content

Add unit tests for policies/yum.go#952

Open
ganochenkodg wants to merge 4 commits intoGoogleCloudPlatform:masterfrom
ganochenkodg:policies-yumchanges
Open

Add unit tests for policies/yum.go#952
ganochenkodg wants to merge 4 commits intoGoogleCloudPlatform:masterfrom
ganochenkodg:policies-yumchanges

Conversation

@ganochenkodg
Copy link
Copy Markdown
Contributor

!!! Merge and review only after PR 949
Depends on expectedCommand and setExpectations from policies/policies_test.go

New test coverage:
github.com/GoogleCloudPlatform/osconfig/policies/yum.go:68: yumChanges 100.0%

@google-oss-prow
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ganochenkodg
Once this PR has been reviewed and has the lgtm label, please assign ekremenetskii for approval. 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

@google-oss-prow
Copy link
Copy Markdown

Hi @ganochenkodg. Thanks for your PR.

I'm waiting for a GoogleCloudPlatform 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.

Comment thread policies/yum_test.go
Comment on lines +92 to +94
rpmQueryArgs := []string{"--queryformat", `\{"architecture":"%{ARCH}","package":"%{NAME}","source_name":"%{SOURCERPM}","version":"%|EPOCH?{%{EPOCH}:}:{}|%{VERSION}-%{RELEASE}"\}` + "\n", "-a"}
yumCheckUpdateArgs := []string{"check-update", "--assumeyes"}
yumListUpdatesArgs := []string{"update", "--assumeno", "--color=never"}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Why don't we use existing variables defined in yum.go ?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

because we try to avoid changing the original code. they are placed in different package ("packages", not "policies") and start from small letters -> can't be imported without renaming. Should we update yum.go?

@burov
Copy link
Copy Markdown
Member

burov commented Apr 17, 2026

/gcbrun

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