Message content assertion defaults to null after restart

Hi,

As a reminder if you are a SoapUI Pro user you can post in the Pro forums.
I was able to reproduce the problem with message content assertion.
I did not see anything showing as null, for me it is not keeping the changes to the assertion on restart.

Can you post a screen shot of the null you are seeing?

Hi James,

The message content assertion is not saved for me to on exit.
Is the behaviour correct, as iam a first time user of the tool.
This breaks my test.

I have attached a screen shot of assertions and when the assertion is null it's not editable.

Hi,

The message content assertion changes are actually saving for me today upon exiting and restarting SoapUI Pro.

So, are you saving your project before exiting SoapUI?

Is this test step a cloned teststep i.e a copy of another test step?
Did you change the ordering of this test step in the project navigator?

Also please attach your project if possible, for further diagnosis.

My Autosave interval is for 5 minutes so it does save it. I do save all the projects before exit.
Yes, it's a cloned test step but under a test case i have only one step.
I actually din't change any ordering but yes i have added new projects.

Actually if you think there are some issues which trigger the the Message content assertion not to save the nodes or what the best practices are then i can try it and let you know?

Iam sorry project cannot be sent or uploaded here.

Hi,

There is an internal bug SOAP-822 which has been reported that the assertion breaks when used in a cloned test case and moved around in the project navigator. The problem you are currently facing may be related to that bug. I used a test step created from "scratch" with the assertion. So try to create the test step without cloning, create the assertion, and see if changes are saved.