Good to know. I might check this out if our workaround of using an old Postman version (before the scratch pad issue) stops working.
Old Postman is a great API testing tool. We used to work with SoapUI, but the license is expensive and tests required a programming language nobody really knew. It was more for exploratory testing and could only be used by one person. Switching to Postman was really worth it. Now everybody could work on it, we could automate with it and the languages used were the same ones as in our product.
Hey folks, i recently created an API testing tool with integrated mock services specifically catering to QA folks for API testing needs. It would be great if someone can give some feedback on this and love to hear from you guys if this is something i should spend any time further
I see a lot of people were switching to Bruno recently because they are disappointed by what Postman did.
It is open source, has desktop app, cli and VS Code extension, Git support. https://www.usebruno.com/
We use Postman as it is a tool that all the devs and testers know well, in a language - javascript - that everyone in the team understands. However it’s UI and variable model doesn’t lend easily to modular code for the kinds of tests I like to write, so I am considering just using a straight framework i.e. RestAssured or even Cypress instead.
I would not say I have a favourite API testing tool. I use what is already on the project, or if I’m starting anew, I use whatever suits best for the needs of the team.
I love(d) Postman for quick API exploration, but contrary to other posters, I would not consider it a good automation tool - don’t get me wrong, I have close to 200 tests in Postman collections but when you need to work with git and CI, it is not an ideal choice.
I also loved Puppeteer, however I think Playwright is gaining advantage over it.
Chai is my library of choice for asserting API response.
My team uses postman but I prefer doing things a bit manually using supertest JS.
It allows me to get only necessary fields in a large list of results.
But wait, can you do that in postman too?
Btw these days we’re writing API tests in Playwright. In one of my github projects I’ve implemented some basic ones.
In my rudimentary TypeScript Test Framework, I use Jest with supertest and chai.
I was thinking of migrating my Webdriver IO project to typescript and then use some additional tools for API requests. Since I already have experience with SuperTest I can make use of such a combination.
I most definitely support migration to TypeScript, it gives you much more power and control of your test data as well as all the objects that you create, like HTTP Requests and Responses.
Just consider carefully if WebdriverIO is the right tool for API requests. It is browser/UI-oriented, like Selenium, Playwright, Puppeteer and others.
I chose Jest cause:
devs are using it and can jump in and help at any time
we do not have any UI, just API tests which is much easier
Tradeoff we had to deal with was the fact that Jest is not fully fledged Test Framework, running multiple suites with global setup/teardown and reporting can be challenging to set up.
I already have API tests implemented in playwright and they work like a charm.
I’m webdriver IO for appium automation so I needed some API calls for basic teardown operations.
Nowadays my default API testing tool would be Apidog. Although pretty new, I think its clean and simple user interface really supports learning a new environment, and I love that it has satisfied all my needs for everything API related.
However, I do hear a lot of other popular alternatives, like Hoppscotch, Bruno, and Insomnia. If you need help, I am confident that a strong community is ready to help you.
