API developers split testing across tools when clients lack key controls
API developers report gaps in their testing tools around concurrent requests, chunked or streaming traffic, varied request bodies, file-driven test runs, and network simulation. They work around these gaps by switching tools, recreating requests, or writing code, making it harder to keep test cases in one workflow. The Undici mocking request is at a different layer—Node.js tests—but most of the signals concern running or controlling API tests.
For API developers and testers. Mentioned from Oct 2017 to Nov 2024 on GitHub and Stack Exchange.
8 different people described this problem in 7 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.5/10
- Frequency
- 7.9/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
So I want to find a load testing tool which can: - support all these protocols; - wait for a specified chunk (it's OK if I have to specify the number but better by content)
I tried Postman, but it only supports serial testing, not parallel. I also tried JMeter, but the experience wasn't very good
Build brief
See what to build and who will buy it
- 2 product ideas with the smallest useful version and pricing
- 4 places to find your first customers
- 6 more quotes from people who have this problem
- Current workarounds, existing solutions and risks