30 Days of API Testing Day 22: Share your biggest frustration with API testing!
Since I learnt API testing, the biggest frustration with it maybe it is difficult to debug the failing API Tests. Currently I’m getting an issue with the Exercise 3
For me, it’s APIs with hidden dependencies. I recently ran into issues with one that required authorization and a small number of other properties before any of the published calls could succeed - but did not provide an endpoint to perform said authorization and property-setting.
That API could not be tested in isolation, and I spent a frustrating few days before I discovered this.
One of my frustrations with API testing is setting up enough mocks to isolate the code under test. Managing the mocks becomes challenging as an API grows!
I agreed with @devtotest, managing mocks is one of challenges when perform API testing. We are applying Scrum framework and Agile methodology to develop our software. The consequence of emerging products from Sprint to Sprint is Data modal changed. Therefore, managing and maintaining mock data is my biggest frustration.
On my project we use third party api which communicate with our server. There are plenty of cases when it responds with such data that our server cannot process correctly. As a result we should to commit hot fixes on production. The challenge is that we never can foresee these cases.
From our friends on Twitter
My biggest frustration is errors when run projects because I’ll take time to investigate to fix them
When I have issues, I try to debug step by step but it is impossible although I tried many ways. This is my biggest frustration.
I just run some requests for API Testing, so my current frustration is every time having an issues on running, it’s difficult to look for the cause and the solution.
At the first day in API testing, my biggest frustration with API testing is analyze when an API return error. I was not sure if the error come from my mistake (executing the call with wrong parameter, missing header, missing auhenToken…) or not. Some time it was from my mistake sometime not. So I was taken a lot time to investigate it.
My biggest frustration with API testing is analyze issues when an API return error because i’m not sure this issue come from the API or my mistake. this many take times!
The second is working on API we just communicate with API with the method(POST/GET) and see the result returns values. Working on the NO GUI environment make some tired :))lol.
In the past couple of months since I started working with APIs one of my biggest frustrations with API testing has been inconsistent response formats and responses that return little to no data regarding the end result of the process (e.g. IDs and other values associated with objects created)
Top 3 frustrations with API testing for me
No Documentation - I mean it is fun to find out what the API is and what it can do but you can only get so far on your own
Poor Documentation - Having Documentation that is only partly ready makes your life really not fun
Too Standard responses for Error Scenarios. I mean somenthing went wrong is really nice if you want to know what is wrong
Top frustration of api testing:
- All of the logic is in the UI and not on the API