-
Notifications
You must be signed in to change notification settings - Fork 114
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
Increase end-to-end test coverage #529
Conversation
Thanks for your PR,
To skip the vendors CIs use one of:
|
Thanks for your PR,
To skip the vendors CIs use one of:
|
Pull Request Test Coverage Report for Build 6796186050
💛 - Coveralls |
Thanks for your PR,
To skip the vendors CIs use one of:
|
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.
Looking good for the LogLevel stuff minus the "FIt" / "It" in test_sriov_operator.go on line 111
@@ -108,7 +108,7 @@ var _ = Describe("[sriov] operator", func() { | |||
Describe("No SriovNetworkNodePolicy", func() { | |||
Context("SR-IOV network config daemon can be set by nodeselector", func() { | |||
// 26186 | |||
FIt("Should schedule the config daemon on selected nodes", func() { | |||
It("Should schedule the config daemon on selected nodes", func() { |
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 don't want to be pedantic but instead of FIt
in the previous commit and then moving it back to It
it in this commit, wouldn't it be better to rebase and make sure that it's always It
in both commits?
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.
sure, it's better to make it clean
Add a basic assertion in the end-to-end suite to verify that the config-daemon is able to publish k8s Events. Signed-off-by: Andrea Panattoni <[email protected]>
Thanks for your PR,
To skip the vendors CIs use one of:
|
From my side (sriov logging) lgtm |
Add an end-to-end test to verify that configuring the LogLevel field of a SriovNetwork makes sriov cni Add command logging to multus pods Signed-off-by: Andrea Panattoni <[email protected]>
Thanks for your PR,
To skip the vendors CIs use one of:
|
LGTM |
Add a basic assertion in the end-to-end suite to
verify that the config-daemon can publish
k8s Events.
cc @rollandf
Add an end-to-end test to verify that configuring the LogLevel
field of a SriovNetwork makes sriov cni Add command logging
to multus pods
cc @andreaskaris