The way I test APIs looks so different now :) I make Claude write and run tests. I do not think I, or anyone, will ever write cURL or equivalent commands or use a tool in the near future.
My workflow is now simple. Once all the core business logic is checked in and I am ready to test stuff, this is what I do:
- make claude write tests
- ensure it covers a good chunk of code
- make claude write a test spec
- spec has endpoints, responses, and potential errors
- claude creates a testing-md file with key details
- claude uses this file for every change, runs the relevant tests, and this keeps tests updated
That is it.
For me, claude code handles the mechanics - making HTTP requests, checking status codes, asserting on response shapes. I handle the judgment - whether the test cases actually cover what matters.
The split works well because neither side is doing the other’s job. (I just realised I am treating it like a co-worker).
Given, claude can translate spec or even a thought into test code faster than I can set up any GUI tool, why do things manually :) By the way, the spec also doubles as documentation, which is a free side effect.
Whether Claude uses pytest, go test, requests, httpx, or raw cURL under the hood does not matter to me. What matters is that the tests run, fail loudly when they should, and take minutes to write instead of an afternoon.
I do not think I will open an API testing tool again. Writing the test logic was always the slow part. That problem is mostly gone now.
I am getting AI-pilled, I guess :)