-
Notifications
You must be signed in to change notification settings - Fork 460
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 crictl config
e2e tests
#1659
Conversation
Signed-off-by: Sascha Grunert <[email protected]>
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kwilczynski, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Expect(cfg).To(MatchRegexp("timeout .* 10")) | ||
}) | ||
|
||
It("should succeed to set config values and preserve comments", 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 wonder how it will treat duplicate entries.
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.
It will only change the first one, which is a bug. Going to fix that in #1661
Expect(cfg).To(MatchRegexp("timeout .* 10")) | ||
}) | ||
|
||
It("should succeed to set config values and preserve comments", 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 know if preserving comments is a valuable feature. But I can see how it may be useful and some people relying on it, thank you for adding a test!
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Adding e2e tests for the config get / set.
Which issue(s) this PR fixes:
Follow-up on #1643
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?