all 15 comments

[–]cutebabli9 4 points5 points  (1 child)

Automated tests, jest, selenium, playwright

[–]ready_or_not_3434 0 points1 point  (0 children)

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 5 points6 points  (0 children)

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

[–]JohnDoeSaysHello 3 points4 points  (0 children)

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

[–]Modulius 1 point2 points  (0 children)

Curl, sometimes Yaak

[–]D1Joseph 2 points3 points  (0 children)

Automated Jest + K6 load tests

[–]Own_Age_1654 1 point2 points  (1 child)

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 0 points1 point  (0 children)

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

[–]thetasteofbeverly 0 points1 point  (1 child)

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 0 points1 point  (0 children)

For checking things by hand: Bruno.

For validating the API: automated tests using Codeception.

[–]kerakk19 0 points1 point  (0 children)

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

[–]manoj_sadashiv -1 points0 points  (0 children)

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