-
Notifications
You must be signed in to change notification settings - Fork 6
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
Removing httpretty #4
Conversation
…ways an Authorization problem)
This PR is ready for review - however, tests will fail until qiita-spots/qiita#1862 is merged. |
@josenavas, could you let us know when tests pass? Thanks. |
Passed! |
@@ -158,80 +132,69 @@ def test_patch_value_error(self): | |||
# Add, replace or test | |||
with self.assertRaises(ValueError): | |||
self.tester.patch( | |||
'/qiita_db/artifacts/1/filepaths/', 'add', '/html_summary/', | |||
'/qiita_db/artifacts/1/', 'add', '/html_summary/', |
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.
So filepaths is not being tested anymore?
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.
The filepaths endpoint no longer exists. In any case, this is just checking the patch
functionality of the qiita_client, so the only thing that I needed is an endpoint that allows patching.
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.
ok, thanks.
1 question. |
This PR removes the mock REST api using httpretty and uses the local installation of Qiita to test the plugin.
Currently I've only modified one test to check if it works as expected, I will modify the other ones once I know this works.