-
Notifications
You must be signed in to change notification settings - Fork 244
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 more tests for Podman + write Component abstraction for integration tests #6427
Add more tests for Podman + write Component abstraction for integration tests #6427
Conversation
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
3cc4d55
to
2177bba
Compare
Kudos, SonarCloud Quality Gate passed!
|
|
||
func (o *PodmanComponent) ExpectIsNotDeployed() { | ||
podName := fmt.Sprintf("%s-%s", o.name, o.app) | ||
cmd := exec.Command("podman", "pod", "list", "--format", "{{.Name}}", "--noheading") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to make the path to podman
configurable (ideally using the PODMAN_CMD
env var just like with the internal PodmanCli
client)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure. This is used during integration tests only, on a stable environment, I cannot see a reason for the moment to have to configure it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree from the environment perspective.
I thought it would make sense for an odo
dev to make sure the same podman binary is used when running the actual odo
commands in the tests and when performing the assertions here..
But okay, that's something that can be optimized later on.
/lgtm
Looks like an infra error on Prow. And all tests are passing on IBM Cloud. /override ci/prow/v4.11-integration-e2e |
@rm3l: Overrode contexts on behalf of rm3l: ci/prow/v4.11-integration-e2e In response to this:
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. |
/override ci/prow/v4.11-integration-e2e |
@feloy: Overrode contexts on behalf of feloy: ci/prow/v4.11-integration-e2e In response to this:
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. |
What type of PR is this:
/kind tests
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes partially #6416
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: