Forum Discussion
If I might ask, what is causing the changes to the response payload structure?
Planned sprint work...
The the response payload itself is being changed based upon business needs however we often have many many tests that are consuming that API call and asserting on fields that now may be renamed/removed etc.
- Lucian6 years agoCommunity Hero
Another thing that may help is to use dynamic assertions instead of fixed assertions. This is possible in XPath as well in JSONPath :smileyhappy:. So the assertions won't fail each time when something is changed, well at least they won't fail when something is added or removed from the current response.
Cheers!
- Olga_T6 years agoSmartBear Alumni (Retired)
Hi all,
Thank you so much for your assistance, Lucian and groovyguy!
kenm, is the issue solved? Or, are there any additional details on the matter?We are looking forward to hearing from you,
- kenm6 years agoContributor
I'm afraid it's not resovled.
My assertions themselves are quite granular. On specific fields existence and values... however if the root path of that response structure changes then naturally they start to fail. If this payload response (and assertions) are present in a considerable number of testcases then it'd be helpful to have some sort of global search/global search and replace capabilies.
Related Content
Recent Discussions
- 18 hours agodipsthorat
- 22 hours agoisbiat
- 2 days agoarmygrad