httparty VS vcr

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:

Basically, it's a record/replay tool, similar to VCR for Ruby, but on steroids and powered by AI (khm GPT khm).

I don't think it's right to say "pythagora generates integration tests". It's more of a "replay manual tests as fixtured unit tests," which makes it similar to (but more powerful than) VCR for Ruby HTTP. What I've always wanted for these kinds of "request recorders" is a way to re-validate the test fixtures over time.

For example, they might expect to be able to mock calls to your API with something like VCR or Responses.

I also started from the same starting point but then discovered and started using VCR for creating http stubs - https://github.com/vcr/vcr. It allowed me to write against more realistic and complex test scenarios but didn't support databases.

If you had bit more complex workflows or less time - you could start using a VCR library to mock out API interactions and then continue with your dockerised DBs.

I generally will use vcr[0] or something similar to record requests and then I write tests and code against that.

3rd parties go down, it happens. In general a system that is dependent on a third party should have some non exceptional behavior when that happens.

So if I’m not setup with vcr, and 3rd party is down- I would on the behavior for what happens when it’s down.

[0] https://github.com/vcr/vcr

With external APIs, you can also make use of a gem like VCR. I prefer mocks (plus unit tests around the actual deserialization of the response) to VCR in most cases, but the end result is about the same.

A way to avoid this is using the VCR gem.

We'll use a tool called vcr to capture real HTTP requests and responses, storing and using them from then on. VCR's language and terminology leans heavily into its real-world analogue. If you don't know what a VCR is, it's a box we used to hook up to TVs to watch movies before DVD players. If you don't know what a DVD player is, it's a box we used to hook up to TVs to watch movies before streaming.

[1] https://github.com/vcr/vcr