How do you manage and test API calls workflows?

I’m building a pipeline where Julia pulls in and sends out data via HTTP. Curious how others test their API logic — inside Julia or with external tools? Looking for fast and flexible solutions.

Some options include:

  • Have a locally hosted version of the service you are testing against (if the service is yours).
  • Create a mocked version of the service and locally host that.
  • Use something like BrokenRecord.jl to automatically mock out the service by recording real responses from the real service.

And in general factor your code so that the actual API calling bit is as small as possible, so you can write true unit tests for everything else, and only rely on integration tests like this to test the actual API calling.

3 Likes

This is quite old, but very informative example: MusicAlbums.jl/src/Client.jl at master · quinnj/MusicAlbums.jl · GitHub

2 Likes

I’ve run into the same thing while working with HTTP.jl. For quick tests and sanity checks, I still lean on external tools — Bruno is nice and lightweight, and I’ve also tried Apidog recently, which feels like a middle ground between Postman and more minimal setups. It supports collections and testing flows pretty smoothly. Curious what others are using too

1 Like