-
Notifications
You must be signed in to change notification settings - Fork 350
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: e2e kamel cli tests #2126
Conversation
e2e/common/cli/delete_test.go
Outdated
Expect(Kamel("delete", "yaml", "-n", ns).Execute()).To(Succeed()) | ||
Expect(GetOutputString(Kamel("get", "-n", ns))).ShouldNot(ContainSubstring("yaml")) | ||
Expect(Kamel("delete", "java", "-n", ns).Execute()).To(Succeed()) | ||
Expect(GetOutputString(Kamel("get", "-n", ns))).ShouldNot(ContainSubstring("java")) |
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.
@vsokolov00 Since focus of this test is kamel delete
you should verify that the integration resource and the pod were actually removed rather than kamel get
command output.
e2e/common/cli/delete_test.go
Outdated
@@ -38,20 +38,20 @@ func TestKamelCLIDelete(t *testing.T) { | |||
Expect(Kamel("run", "-n", ns, "../files/yaml.yaml").Execute()).To(Succeed()) | |||
Eventually(IntegrationPodPhase(ns, "yaml"), TestTimeoutMedium).Should(Equal(v1.PodRunning)) | |||
Expect(Kamel("delete", "yaml", "-n", ns).Execute()).To(Succeed()) | |||
Expect(GetOutputString(Kamel("get", "-n", ns))).ShouldNot(ContainSubstring("yaml")) | |||
Eventually(Integration("yaml", ns)).Should(BeNil()) |
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.
@vsokolov00 can you verify that the IntegrationPod was removed as well?
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.
done, please check if everything is ok in the latest commits
Could you please rebase, and make sure to remove the extra merge commit "Merge branch 'e2e-test-cli'"? |
Done :) the history is clean now |
e2e/common/cli/get_test.go
Outdated
Expect(Kamel("run", "../files/yaml.yaml", "-n", ns).Execute()).To(Succeed()) | ||
Eventually(IntegrationPodPhase(ns, "yaml"), TestTimeoutLong).Should(Equal(v1.PodRunning)) | ||
str := GetOutputString(Kamel("get", "-n", ns)) | ||
Expect(str).Should(ContainSubstring("yaml\tRunning\tkit-")) |
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.
You can check the whole kit name. Integration("yaml",ns)().Status.Kit
@oscerd Could you run the tests again please? |
Restarted. |
@oscerd tests on k8 were successful, made some changes to adjust the test suit to the openshift, but failure of builder-it (Buildah) was not affected by my changes, seems that there were some problems with github/dockerhub packages or sth. Could you run the pipe one more time please, hopefully the last one 😄 |
The root cause of the issue with running the
A possible solution would be to create a separate Viper instance, for each command execution. |
Superseded by #2422. Tests for the |
PR for
https://issues.redhat.com/browse/FUSEQE-12050
https://issues.redhat.com/browse/FUSEQE-12051
https://issues.redhat.com/browse/FUSEQE-12052
Release Note