Flowtest
Continuously test your APIs, catch regressions before anyone
Flowtest started from a problem I experienced while working with banking APIs.
Testing asynchronous workflows manually was slow and repetitive. A single test could involve several API calls, waiting for background processes, checking statuses, copying values between requests, and repeating everything whenever something changed.
Existing tools were useful for individual requests, but I wanted a simple way to describe and automate the complete workflow.
That became Flowtest: a tool for building end-to-end API tests with requests, variables, assertions, waits, and polling. Tests can then run continuously to catch regressions.
I’ve been building it gradually around real API testing problems, and I’m now sharing it publicly to learn how other developers and teams test their APIs.
I’d love to hear how you currently test complex or asynchronous API workflows.
3 Comments
The interesting transition here is from solving a workflow you personally experienced to finding out how broadly that same pain exists elsewhere.
From the developers or teams you've shown Flowtest to so far, are you seeing the same asynchronous-testing problem appear independently, or does it mostly resonate once you demonstrate the product?
Hi Aryan, thank you for your question!
Yes, when I set up a flow for other developers and teams, they experience the same pain and find it extremely useful when something fails, because it is very easy to find the exact request and response and resolve the issue. It works also for sync flows.
The flow runs every minute, and a notification is sent as soon as it starts failing.
Do you have any public or private API to test?
Thanks for explaining. I don’t have an API I can test right now, but I was mainly interested in the validation side — whether teams were recognizing this pain before seeing Flowtest or only after experiencing the workflow.
The independent recognition of the problem is the interesting signal.