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 test case for ToValidOperationID method: TestToValidOperationID #109690

Merged
merged 1 commit into from
Jul 23, 2022

Conversation

twilight0620
Copy link
Contributor

What type of PR is this?

add test case for ToValidOperationID method: TestToValidOperationID

Add one of the following kinds:
/kind cleanup

What this PR does / why we need it:

ToValidOperationID method does not has ut test, so i add it.

Which issue(s) this PR fixes:

add ut test

Special notes for your reviewer:

Does this PR introduce a user-facing change?

  NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

@k8s-ci-robot
Copy link
Contributor

Please note that we're already in Test Freeze for the release-1.24 branch. This means every merged PR has to be cherry-picked into the release branch to be part of the upcoming v1.24.0 release.

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 27, 2022
@k8s-ci-robot
Copy link
Contributor

Hi @twilight0620. Thanks for your PR.

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

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.

@k8s-ci-robot k8s-ci-robot added needs-priority Indicates a PR lacks a `priority/foo` label and requires one. area/apiserver labels Apr 27, 2022
@k8s-ci-robot k8s-ci-robot added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 27, 2022
@yxxhero
Copy link
Member

yxxhero commented Apr 27, 2022

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Apr 27, 2022
@twilight0620
Copy link
Contributor Author

pull-kubernetes-verify

@yxxhero hi, i see some checks were not successful, but i did not see errors about my ut code, does the failures caused by my code? what should i modify?

@yxxhero
Copy link
Member

yxxhero commented Apr 28, 2022

/retest-required

@yxxhero
Copy link
Member

yxxhero commented Apr 28, 2022

@twilight0620
Copy link
Contributor Author

/retest-required

@leilajal
Copy link
Contributor

/assign @Jefftree @apelisse
/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 28, 2022
@apelisse
Copy link
Member

/assign @Jefftree

Do you want to look at this?

@Jefftree
Copy link
Member

@twilight0620 Since we're adding tests to improve the coverage, can we add test cases to exercise all code paths of the function?

(Add cases for names with underscore and numbers https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/endpoints/openapi/openapi.go#L47)

Thank you!

@Jefftree
Copy link
Member

/unassign @apelisse

@twilight0620
Copy link
Contributor Author

@twilight0620 Since we're adding tests to improve the coverage, can we add test cases to exercise all code paths of the function?

(Add cases for names with underscore and numbers https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/endpoints/openapi/openapi.go#L47)

Thank you!

ok, i have added it.

@twilight0620
Copy link
Contributor Author

/retest-required

@Jefftree
Copy link
Member

@twilight0620 Since we're adding tests to improve the coverage, can we add test cases to exercise all code paths of the function?
(Add cases for names with underscore and numbers https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/endpoints/openapi/openapi.go#L47)
Thank you!

ok, i have added it.

Sorry if I wasn't very clear, you don't need to add a separate test case for those behaviors in isolation. Bundling them with one of the other test cases should be fine.

@twilight0620
Copy link
Contributor Author

@twilight0620 Since we're adding tests to improve the coverage, can we add test cases to exercise all code paths of the function?
(Add cases for names with underscore and numbers https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/apiserver/pkg/endpoints/openapi/openapi.go#L47)
Thank you!

ok, i have added it.

Sorry if I wasn't very clear, you don't need to add a separate test case for those behaviors in isolation. Bundling them with one of the other test cases should be fine.

you mean add scenarios like abc_abc and abc33abc?

@twilight0620
Copy link
Contributor Author

/retest-required

@twilight0620
Copy link
Contributor Author

could anyone handle and merge this pr?

@apelisse
Copy link
Member

apelisse commented Jun 8, 2022

gentle ping @Jefftree

@Jefftree
Copy link
Member

Jefftree commented Jun 8, 2022

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jun 8, 2022
@Jefftree
Copy link
Member

Jefftree commented Jun 8, 2022

/assign @sttts

@twilight0620
Copy link
Contributor Author

gentle ping @sttts

@twilight0620
Copy link
Contributor Author

/assign @smarterclayton

@sttts
Copy link
Contributor

sttts commented Jul 22, 2022

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sttts, twilight0620

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

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 22, 2022
@k8s-triage-robot
Copy link

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

  • The PR does have any do-not-merge/* labels
  • The PR does not have the needs-ok-to-test label
  • The PR is mergeable (does not have a needs-rebase label)
  • The PR is approved (has cncf-cla: yes, lgtm, approved labels)
  • The PR is failing tests required for merge

You can:

/retest

@k8s-ci-robot k8s-ci-robot merged commit 455c1c2 into kubernetes:master Jul 23, 2022
@k8s-ci-robot k8s-ci-robot added this to the v1.25 milestone Jul 23, 2022
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. area/apiserver cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none Denotes a PR that doesn't merit a release note. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

9 participants