httparty VS WebMock

I would grab a gem like httparty, and dive into the API docs and see what you can do.

HTTParty — Used to make HTTP requests and fetch the required data.

Usually, my ruby HTTP library of choice is HTTParty but I wanted to set this up using the ruby Net::HTTP lib to keep from introducing another dependency.

Everyone here seems to have misread what you wanted. From my interpretation, you are trying to upload a csv somewhere, using an api. With ruby, you can either do it with a built in library or one of the nice http gems. Someone suggested using Python with a builtin library called requests which isn't actually built in, so I'm also going to go with a library that isn't built in. httparty

My go-to is HTTParty for most cases. As a simple example for a one-off request:

I'm too tied to the implementation. If one day I decide to use Faraday or HTTParty as my HTTP clients instead of Net::HTTP, this test will fail.

httparty gem

Now we ensured the right meta data is added to the emails with a custom metatag, let's setup the Postmark API to retrieve the email data an show it in our application. The first step is to add a gem so we can send HTTP requests to the Postmark API. There are several good gems for this, I use the httparty gem. So add this to the Gemfile:

If you want to check out an alternative to VCR, have a look at webmock.

Well, that's why your test says: "When the API responds like this I do that". People hate on ruby but webmock makes it very nice to mock/stub that, or for python there's responses. For the database you can use a local database with factories to easily create the data you need for each test and clear it between tests.

Man if you think python has great mocking/testing support, you check out some ruby tests! Honestly some of the best testing libraries that pioneered approaches that are becoming more common elsewhere, such as the expectations syntax. And now that I'm coding more in python I find myself missing libaries like webmock, letting you stub web reqests in a way that's agnostic of the HTTP/web libary, chef's kiss.

In order to keep our test suite faster and consistent, we need to mock our http requests. A simple and good way to achieve this is using the Webmock gem which allow easily mock the http responses for your requests.

We can avoid managing HTTP communication with our dependency. Instead, we'll stub out how we expect it to respond. In this case, we'll use webmock to stub out a response at the HTTP layer.

The other option is to mock the web requests to Hetzner - this: https://github.com/bblimke/webmock or similar may help.

There are fine istructions in WebMock README. I want to share it here for reference:

You can find the setup instructions and examples on how to use WebMock, in their github documentation. WebMock will prevent any external HTTP requests from your application so make sure you add this gem under the test group of your Gemfile.