Just a message to let anyone following this topic know that it was indeed fixed with release 1.4, which is now available :).
Here's an update in case anyone else is impacted by this issue: the developers were able to reproduce it, and found out that it existed at least since SoapUI PRO 5.1.2. It will be fixed in one of the next versions.
Once again Jeshtha, thanks for your help!
Yeah, this extremely annoying bug has been around since at least 2013 but probably longer and was denied/ignored back then. They should release a patch for the 1.2 version since 1.3 contains serious mem leaks and is unusable for that reason (of course, that issue is also being denied/ignored) and come to think of it, fix the whole UI so it stops crashing every 10 minutes.
The whole idea of having a project file in XML is wrong and the fact that SoapUI corrupts it every now and then is downright frustrating. Clone a test step, restart the application and your message content assertions are all null! Seriously???
Just a message to let anyone following this topic know that it was indeed fixed with release 1.4, which is now available :).
