Forum Discussion
One quick way to update it, if you know what changes need to be made, is to write a groovy script to parse every test step and its assertions in a project and change the contents of the script assertion. Or to open the XML file itself (if its not a composite project) and do a find/replace all.
Within ReadyAPI itself, depending on the cause that is driving your changes, if you have to update/wsdl/schema you can use the "Refactor" option to potentially update XPATH within all of the assertions.
Can you provide a bit more detail? What is driving your change and what do you need to change on the assertions?
- kenm7 years agoContributor
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.
- groovyguy7 years agoCommunity Hero
If I might ask, what is causing the changes to the response payload structure?
- kenm7 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.
Related Content
- 9 years ago