2 hours ago
Genuine question for the folks here doing QA or backend work. Our team just did an internal audit and we're somehow running four different tools for API testing. One for manual poking at endpoints, one for the automated suite in CI, one just for mocking, and one somebody added last year that I'm not sure anyone still uses.
I started reading up on what's out there now and found a pretty thorough roundup of api testing tools that covers both the established stuff and the newer open source options that generate tests from recorded traffic instead of making you write everything by hand. The AI-assisted direction is interesting but I can't tell yet how much is real and how much is marketing.
So I'm curious how others handle this. Did you standardize on one tool for everything, or do you accept that manual testing and CI automation just need different tools? And if you consolidated, what did you keep?
I started reading up on what's out there now and found a pretty thorough roundup of api testing tools that covers both the established stuff and the newer open source options that generate tests from recorded traffic instead of making you write everything by hand. The AI-assisted direction is interesting but I can't tell yet how much is real and how much is marketing.
So I'm curious how others handle this. Did you standardize on one tool for everything, or do you accept that manual testing and CI automation just need different tools? And if you consolidated, what did you keep?