You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please fill out the issue checklist below and provide ALL the requested information.
I reviewed open and closed Github issues that may be related to my problem.
I am reporting a bug that others will be able to reproduce.
Describe the bug
When running integration test (make integration-test) against tap cluster it fails when asserting in the command tanzu apps cluster-supply-chain list and tanzu apps cluster-supply-chain get ci-test
Expected behavior
All the integration test pass
Steps to Reproduce
Steps to reproduce the behavior:
configure a TAP cluster
run make integration-test
Screenshots
Version (Apps plugin version, Version of K8s running on cluster)
Put the output of the following commad
tanzu version && tanzu apps version
N/A
Environment where the bug was observed (cloud, OS, etc)
When the integration test configures the environment to run the test cases, it creates a cluster supply chain and a test namespace, the test try to list the existing supply chain and get the details of the created one by checking the output of the command, those test must do a more interactive comparison instead of an exact match because depending on the target cluster which is used to the test may differ from expected.
Create some utilities or use golang structures to parse each get/list output
The text was updated successfully, but these errors were encountered:
atmandhol
changed the title
Improve integration test validation agains tap cluster
Improve integration test validation against TAP clusters
Jul 26, 2022
Please fill out the issue checklist below and provide ALL the requested information.
Describe the bug
When running integration test (
make integration-test
) against tap cluster it fails when asserting in the commandtanzu apps cluster-supply-chain list
andtanzu apps cluster-supply-chain get ci-test
Expected behavior
All the integration test pass
Steps to Reproduce
Steps to reproduce the behavior:
make integration-test
Screenshots
Version (Apps plugin version, Version of K8s running on cluster)
Put the output of the following commad
tanzu version && tanzu apps version
N/A
Environment where the bug was observed (cloud, OS, etc)
Additional context & Relevant Debug Output (Logs, etc)
Add any other context about the problem here.
When the integration test configures the environment to run the test cases, it creates a cluster supply chain and a test namespace, the test try to list the existing supply chain and get the details of the created one by checking the output of the command, those test must do a more interactive comparison instead of an exact match because depending on the target cluster which is used to the test may differ from expected.
Create some utilities or use golang structures to parse each
get
/list
outputThe text was updated successfully, but these errors were encountered: