Forum Discussion
Cheers for the detailed response,
Typically it's response payload structure changing breaking assertions. That specific call may be used in many many places across the entire solution. We use composite projects so global search and replace on non composite XML not really a runner I'm afraid.
If I might ask, what is causing the changes to the response payload structure?
- kenm6 years agoContributor
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!
Related Content
Recent Discussions
- 16 hours agoKay