-
Notifications
You must be signed in to change notification settings - Fork 137
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
Tink-cli unit tests #366
Tink-cli unit tests #366
Conversation
Codecov Report
@@ Coverage Diff @@
## master #366 +/- ##
=======================================
Coverage 24.74% 24.74%
=======================================
Files 14 14
Lines 1277 1277
=======================================
Hits 316 316
Misses 940 940
Partials 21 21 Continue to review full report at Codecov.
|
Thanks for these coverage improvements, @CarlosOVillanueva! I think the much more interesting parts of this PR are the changes to GetTemplate which appear to fix the name returned by GetTemplate and now include the ID of the template in the response. I'm curious about what benefit this brings. I'm a little detached from this code at the moment, but it looks like the id and name being sent in as required parameters in the If these changes were to appease the tests, I think we should update the tests instead. Affecting the API of the client will have more downstream ramifications as we add clients (tink-cli, terraform, crossplane, etc). Can you offer some explanation for these changes, as it isn't obvious to me? |
@CarlosOVillanueva do you mind rebasing this PR and have a look at the comment @displague left? Thanks a lot |
Let me see what happened there. I suspect that was the result of a merge and me not rebasing the project. I'll fix and resubmit. |
06933b9
to
c615c34
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.
This is testing only helps
commands. It is a bit weird as an assertion but it is a good starting point I presume
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.
LGTM - Thanks, @CarlosOVillanueva !
Signed-off-by: [email protected] <[email protected]>
Signed-off-by: [email protected] [email protected]
Description
Unit tests to validate functionality of tink-cli. These tests do not require external components to be live. They simply test to see if the sub-functions exists and use the help argument to return the description of the command.
Why is this needed
To ensure commands persist between versions.
Fixes: #
How Has This Been Tested?
Run
go test -v
from within cmd/tink-cli/cmdHow are existing users impacted? What migration steps/scripts do we need?
No user impact
Checklist:
I have: