-
Notifications
You must be signed in to change notification settings - Fork 3
Add Integration tests in Python #39
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
ad81174 to
15774ab
Compare
393c871 to
8d21476
Compare
8d21476 to
ca19dbd
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.
Great work, LGTM ✨
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.
Just a couple formatting comments, and one conceptual question.
| """ | ||
| resp = self.api.show_public_keys(self.account, 'Variable', 'one/password') | ||
|
|
||
| self.assertIsInstance(resp, str) |
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.
Not necessarily breaking, but wondering if this assertion actually confirms that the API call worked. Seems a bit too general compared to a lot of the other test cases.
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 test is definitely lighter then others. However I check that the return type is a string because this endpoint is supposed to return a plain text body so I am just making sure that the client returns the proper type. These are just integration tests so I didn't want to add any checks that were too complicated in.
|
Also a rebase, PRs that were open before the GH Action was merged won't be caught. |
ca19dbd to
0695f1e
Compare
Also added an api_config file which will get a default configuration for tests. Should reduce levels of code duplication in the tests
Auto-generated import statements in the test files were causing these messages. Removed them because we cannot change this
Reduces code duplication for the setUpClass and tearDownClass methods
0695f1e to
628b82a
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.
LGTM
No description provided.