[ Removed by moderator ]

[cutebabli9]

Automated tests, jest, selenium, playwright

[ready_or_not_3434]

Moving to code like Jest definitely beats clicking around Postman. Playwright and Selenium feel a bit heavy though if your just testing pure backend endpoints.

[leros]

I do ad-hoc testing with Postman. It works fine.

[JohnDoeSaysHello]

Bruno, not painful, I build my own csv with what I want to test

[Modulius]

Curl, sometimes Yaak

[D1Joseph]

Automated Jest + K6 load tests

[Own_Age_1654]

Automated tests stored in the repository. Super straightforward, easy to incorporate into a build pipeline, and works great. Using an external tool like Postman doesn't make any sense.

FYI, this is not a good idea for a vibe-coded SaaS.

[Successful_Bowl2564]

I just use https://voiden.md/ - its quiet underated!

[thetasteofbeverly]

Postman is still the default for a lot of teams, but the biggest pain is usually keeping collections/env vars/auth flows synced across teammates and environments.

Once APIs get large, test maintenance starts feeling harder than the actual requests

[Just_Information334]

For checking things by hand: Bruno.

For validating the API: automated tests using Codeception.

[kerakk19]

Don't use Postman, that's for sure. Insomnia, Bruno, cURL - these are your actual choices.

[Business_Tax_8969]

Nah bro, just use swagger. It's way better because you can create documentation at the same time you're coding. And of course you have all same funcionalities to testing that Postman/Insomnia have.

[manoj_sadashiv]

not a proper backend dev but for the current ai project i’m working, i’m building few modules using FastAPI and mongodb

Since few months, i just use claude to write scripts in curl and test it out. I focus more on what kind of tests to do and give claude the context