For 1.19.0 build, Pull Ginkgo test cases from argocd-operator repo and integrate them into gitops-operator test structure #1011
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @Naveena-058. Thanks for your PR. I'm waiting for a github.com 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-sigs/prow repository. |
|
/ok-to-test |
Naveena-058
force-pushed
the
pull-ginkgo-tests-from-argocd-operator
branch
2 times, most recently
from
bcd02cc to
7853726
Compare
|
/test v4.19-kuttl-parallel |
|
/test v4.19-kuttl-sequential |
2 similar comments
|
/test v4.19-kuttl-sequential |
|
/test v4.19-kuttl-sequential |
|
/retest |
|
/test v4.14-e2e |
|
/test v4.19-e2e |
|
/test v4.14-kuttl-sequential |
1 similar comment
|
/test v4.14-kuttl-sequential |
|
/retest-required |
|
/test v4.14-kuttl-parallel |
|
/test v4.19-kuttl-sequential |
Naveena-058
force-pushed
the
pull-ginkgo-tests-from-argocd-operator
branch
from
8c70a65 to
97c5c67
Compare
|
/test v4.19-kuttl-sequential |
|
/test v4.14-kuttl-sequential /test v4.14-kuttl-parallel |
Naveena-058
force-pushed
the
pull-ginkgo-tests-from-argocd-operator
branch
from
9a7e5e3 to
8eb1194
Compare
|
/test v4.14-kuttl-sequential |
|
/test v4.14-kuttl-sequential |
|
/test v4.14-kuttl-sequential |
1 similar comment
|
/test v4.14-kuttl-sequential |
|
/test v4.14-kuttl-sequential |
|
/test v4.19-kuttl-sequential |
1 similar comment
|
/test v4.19-kuttl-sequential |
|
/test v4.19-kuttl-sequential |
|
/test v4.14-kuttl-sequential |
2 similar comments
|
/test v4.14-kuttl-sequential |
|
/test v4.14-kuttl-sequential |
|
/test v4.14-e2e |
Naveena-058
force-pushed
the
pull-ginkgo-tests-from-argocd-operator
branch
2 times, most recently
from
38e00f8 to
cd311e6
Compare
Naveena-058
force-pushed
the
pull-ginkgo-tests-from-argocd-operator
branch
from
469f7f8 to
ded3662
Compare
Signed-off-by: NAVEENA S <nas@redhat.com>
Naveena-058
force-pushed
the
pull-ginkgo-tests-from-argocd-operator
branch
from
ded3662 to
b5382de
Compare
|
/test v4.14-kuttl-sequential |
|
@Naveena-058: The following tests failed, say
Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
/test v4.19-e2e |
4 participants
For 1.19.0 build, Pull Ginkgo test cases from argocd-operator repo and integrate them into gitops-operator test structure
What type of PR is this?
What does this PR do / why we need it:
This PR pulls additional Ginkgo test cases from the argocd-operator repository and integrates them into the gitops-operator test structure to improve test coverage for the 1.19.0 build.
Key changes include:
1-046_validate_application_tracking_test.go- Validates application tracking functionality1-122_validate_image_updater_test.go- Tests image updater capabilities1-051_validate_argocd_agent_principal_test.go- Tests ArgoCD agent principal validationfixtureUtils.go1-098_validate_dex_clientsecret_deprecated.goproperly uses deprecated v1alpha1 API for backwards compatibility testing