I would choose your language first, and then a testing toolkit second. REST-assured is cool, but if nobody’s a Java expert, there’s no reason to learn Java just to use it. I’ve done a LOT of API testing over the past 18 years or so, but never have done it with Postman. In my case, it’s always been a matter of developing test automation in whatever the language of choice is - Java, C#, Python. More on reddit.com

The only thing that might be beneficial is mocking the data

More on reddit.com

One of the options I've found is python requests module (allows for sending http requests) in combination with pytest (test runner and assertions) and I kind of like this approach since it feels like i can do things my way rather than conform to the tool like Postman [emphasis added] You've hit the nail on the head. Once you start to do more complex testing, you will hit the limitations of postman very quickly (and spend a lot of time trying to figure out how to work around them). Using a real programming language and rest client library for automation gives you all kinds of flexibility, but of course, the knowledge requirements are higher--you have to know how to program. Edit: this same issue is true for a lot of no-code and low-code automated testing tools in my experience. To answer your question: here's the situation at my employer, manual testing: Postman load testing: gatling (with Java, not scala) AND postman, but we're phasing out postman for the reason mentioned above; it was great to get some tests up and running quickly but we're already hitting its limitations automated functional testing: Java with RestAssured More on reddit.com

Interesting. I use responses for unit tests and directly client of FastAPI for integration tests. I don't see directly a good case for unit tests on my scheme for testing, but maybe for integration tests can be a good case. More on reddit.com