Postman is great for quick testing, but I’m looking to scale up API test automation and integrate more tightly with CI/CD. I’m curious what tools or frameworks others are using.
Are you using REST Assured, Karate, Playwright for API, or something else entirely?
What made you choose it, and how well does it fit into your workflow?
Looking for real-world insights on what actually works.
I use Flurl, Reqnroll, and C# in my current project.
Since we’re a fully backend application, and the development team was already using C# with Flurl, it made sense to align with the same stack so they could easily contribute to the framework as needed.
Our business domain is quite complex, with many moving parts, so we wanted a Business-Driven approach rather than traditional unit tests. Initially, we used SpecFlow (may it rest in peace), but recently migrated to Reqnroll.
Really interesting to see Reqnroll mentioned — hadn’t heard much about it lately, so it’s good to know it’s working well in a complex domain.
On our end, we moved to Apidog for API testing because it helps us go beyond just manual calls like in Postman. We needed something that could support automated testing, mock servers, and better team collaboration. Apidog made it easier to create test cases from our existing API definitions and even run them as part of CI.
What helped us decide:
Still using Postman here and there for quick checks, but for anything that needs to scale with the dev cycle, Apidog’s been more reliable.
Would love to hear if anyone’s combined it with frameworks like REST Assured or Karate too.
Postman / Rester are nice tools to quickly tests APIs and get ideas (exploratory testing). In most cases you need to program the APIs (SOAP) in your test automation suites. If you have done it a few times, implementation is quite fast. In most applications, you require one or many prepare steps to test a API.
for example if you want to test an order of a webshop, you first need to login and make sure that you have items to order and having mocks for the payment server etc. It’s often not that simple to only have simple stand-alone APIs
That makes a lot of sense — aligning with the existing C# + Flurl stack definitely helps with maintainability and team contribution, especially in a backend-heavy environment.
We’ve also been exploring BDD approaches for systems with high domain complexity, and I’m curious how your team found the migration from SpecFlow to Reqnroll.
Yeah, I’ve tested Apidog a little myself — didn’t realize how many teams were already using it until recently. It’s definitely more polished than I expected, especially the way it ties together docs, testing, and mocking in one place.
I’m still exploring how it fits into broader workflows (like combining with REST Assured or similar tools), but it’s great to hear it’s working well for you at scale. Might have to give it a deeper look soon.
Thanks for sharing your experience.
Migration was quite smooth, to be honest. Mostly find and replace. Reqnroll has also published a migration guide which helps a lot.