mdavila
12 years agoNew Contributor
How to quickly resolve assertions affected by schema change
First, I want to make you aware I am a first time soapUI Pro user and run into an issue where we have hundreds of test cases that have xPath assertions. The challenge I am facing is that, I tried Definition Refactoring however, about 95% of the assertions still needed manual editing and I have hundreds of test case assertions to deal with so, while I applaud the good work by the soapUI development and QA team to resolve the issue, it works great when you only have ten to twenty test cases to manually edit.
The next thing I've tried was using ultraEdit by editing the project.XML file and doing a search and replace where the xPath was fixed really fast however, after saving the file and opening with soapUI PRO the file was deemed as corrupted hence, that solution did not work either.
Has this happened to anyone else and if so, is there a way to fix the assertions faster than editing the xPath one test case at a time?
in advance thank you and look forward to hearing a solution.
Thanks,
Misael
The next thing I've tried was using ultraEdit by editing the project.XML file and doing a search and replace where the xPath was fixed really fast however, after saving the file and opening with soapUI PRO the file was deemed as corrupted hence, that solution did not work either.
Has this happened to anyone else and if so, is there a way to fix the assertions faster than editing the xPath one test case at a time?
in advance thank you and look forward to hearing a solution.
Thanks,
Misael