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

test:Add unit tests to jobset success policy functions #491 #493

Conversation

Dibyanshuaman
Copy link

No description provided.

Copy link

linux-foundation-easycla bot commented Apr 3, 2024

CLA Signed

The committers listed above are authorized under a signed CLA.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. label Apr 3, 2024
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Dibyanshuaman
Once this PR has been reviewed and has the lgtm label, please assign danielvegamyhre for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found 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 requested review from ahg-g and kannon92 April 3, 2024 20:01
@k8s-ci-robot
Copy link
Contributor

Welcome @Dibyanshuaman!

It looks like this is your first PR to kubernetes-sigs/jobset 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/jobset has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot
Copy link
Contributor

Hi @Dibyanshuaman. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Apr 3, 2024
Copy link

netlify bot commented Apr 3, 2024

Deploy Preview for kubernetes-sigs-jobset ready!

Name Link
🔨 Latest commit 53d2b4e
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-jobset/deploys/661456b102519d0008ba858c
😎 Deploy Preview https://deploy-preview-493--kubernetes-sigs-jobset.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. and removed cncf-cla: no Indicates the PR's author has not signed the CNCF CLA. labels Apr 3, 2024
@kannon92
Copy link
Contributor

kannon92 commented Apr 3, 2024

/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 3, 2024
@@ -22,6 +22,107 @@ import (
)

// TODO: add unit tests for the functions in this file.
// TestJobMatchesSuccessPolicy tests the jobMatchesSuccessPolicy function.
func TestJobMatchesSuccessPolicy(t *testing.T) {
Copy link
Contributor

Choose a reason for hiding this comment

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

In golang, unit tests are added with a corresponding *_test.go.

So I would move these tests to a pkg/controllers/success_policy_test.go file.

@Dibyanshuaman
Copy link
Author

Dibyanshuaman commented Apr 3, 2024 via email

@danielvegamyhre
Copy link
Contributor

@Dibyanshuaman are you still working on this?

@Dibyanshuaman
Copy link
Author

Dibyanshuaman commented Apr 8, 2024 via email

@kannon92
Copy link
Contributor

kannon92 commented Apr 8, 2024

I +1 the comment. Yes, please move all the unit test into a separate test file. Your PR is failing due to this. Please make sure the CI jobs are green.

@k8s-ci-robot
Copy link
Contributor

@Dibyanshuaman: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-jobset-test-integration-main 53d2b4e link true /test pull-jobset-test-integration-main
pull-jobset-test-unit-main 53d2b4e link true /test pull-jobset-test-unit-main
pull-jobset-test-e2e-main-1-27 53d2b4e link true /test pull-jobset-test-e2e-main-1-27
pull-jobset-test-e2e-main-1-29 53d2b4e link true /test pull-jobset-test-e2e-main-1-29
pull-jobset-test-e2e-main-1-28 53d2b4e link true /test pull-jobset-test-e2e-main-1-28
pull-jobset-verify-main 53d2b4e link true /test pull-jobset-verify-main

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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. I understand the commands that are listed here.

@Dibyanshuaman
Copy link
Author

Dibyanshuaman commented Apr 8, 2024 via email

@kannon92
Copy link
Contributor

kannon92 commented Apr 8, 2024

Thank you @Dibyanshuaman! The CI is failing due to syntax error. Please fix that.

@danielvegamyhre
Copy link
Contributor

@Dibyanshuaman please use table-driven tests to test different scenarios for each function. Example:

tests := []struct {
name string
startupPolicy *jobset.StartupPolicy
expected bool
}{
{
name: "startup policy AnyOrder",
startupPolicy: &jobset.StartupPolicy{StartupPolicyOrder: jobset.AnyOrder},
expected: false,
},
{
name: "startup policy InOrder",
startupPolicy: &jobset.StartupPolicy{StartupPolicyOrder: jobset.InOrder},
expected: true,
},
{
name: "nil startup policy",
startupPolicy: nil,
expected: false,
},
}

@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Apr 11, 2024
@k8s-ci-robot
Copy link
Contributor

PR needs rebase.

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.

@danielvegamyhre
Copy link
Contributor

@Dibyanshuaman are you still working on this?

@danielvegamyhre
Copy link
Contributor

Closing due to inactivity

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants