-
Notifications
You must be signed in to change notification settings - Fork 10k
Tests for query command outputs #37343
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
Conversation
e7fd3fb
to
afb2730
Compare
875323e
to
d2b4619
Compare
d2b4619
to
7822e33
Compare
internal/command/query_test.go
Outdated
t.Fatalf("bad: %d\n\n%s", code, output.Stderr()) | ||
|
||
// Check that we have query output | ||
if !strings.Contains(actual, ts.expectedOut) { |
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 expected this test to fail after merging the updates to the line-based output. However, it appears that this line is never executed. I think the if statements are mixed up here.
Return warning to the CLI if the config has no query files.
7822e33
to
bc8b6c9
Compare
bc8b6c9
to
e835242
Compare
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.
Nice work!
This PR introduces some tests for query command outputs. Also, a warning is returned when the config does not have any list resources.
Target Release
1.14.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry