API testers duplicate setups to cover environment and payload combinations
API developers and testers report having to duplicate environments, collections, or endpoint configurations to test combinations of servers, devices, users, and request bodies. That makes setups harder to maintain and selecting the right tests less clear. Some also want API requests tested alongside network conditions or system-level effects, which may require capabilities beyond a basic request runner.
For API developers and testers. Mentioned from Oct 2016 to Apr 2025 on GitHub and Stack Exchange.
11 different people described this problem in 7 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 6.0/10
- Frequency
- 9.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Businesses
- Competition
- High
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
I have one set of environments for Testing/Stage/Production, and one set of environments for different devices - Android/iOS. I'd like to mix-and-match environments while making requests: Stage+iOS / Production+Android, and avoid creating 3x2 environments to test each combination
abhijitkane on GitHub (postmanlabs/postman-app-support)Aug 2018+99 upvotesAsked for a toolHas a workaroundThe way it is now, I have to have multiple environments with duplicate variables i.e. Test1Device1, Test2Device1, StagingDevice1, Test1Device2,
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 9 more quotes from people who have this problem
- Current workarounds, existing solutions and risks