API testers duplicate shared setup across test collections
API testers using collections for automation duplicate login requests and setup tests wherever they are needed. When a shared request or its pre/post logic changes, they must find and update each copy, making maintenance increasingly error-prone. A related signal points to duplicated resources between unit and end-to-end testing workflows.
For API test automation engineers. Mentioned from Oct 2015 to Oct 2017 on GitHub.
5 different people described this problem in 2 separate discussions.
- Indie fit
- 5.0/10
- Pain
- 5.6/10
- Frequency
- 6.5/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Right now if I need to chain a certain test before other tests in multiple places (say to get a unique id before updating or deleting) I have to duplicate the test. Then if I realize I have an issue in the pre or post logic I need to go through and clean each one individually
If I duplicate the login request, I will have to edit all the requests if I need to change something
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
- 3 more quotes from people who have this problem
- Current workarounds, existing solutions and risks