How do I make SOAPUI save the custom properties after the run?
I have custom properties that are updated during the test run via groovy scripts.
Those values are used during the run. The run works fine. But after is passed, all the custom values that were used during the run are reverted back to old ones.
How do I make it keep the custom properties that are saved and not overwrite them back to a previous runs values?
Or is this a bug? It does seem like a bug but maybe there's an option somewhere.
Solved! Go to Solution.
I'm running from ReadyAPI/SOAPUI Pro.
I don't think I can provide a sample project. But basically the issue is if a test has some values in the custom properties, and I execute a test run where those values are updated, after the run is complete the custom properties are populated with that values that were previous to the test run, and not the values from the test run. I.e it's reverted back to older values for some reason.
I clicked Help > Check for Updates and it says "You are using the latest release of ReadyAPI". However I'm only using 2.8.0 and the update page you sent says 2.8.2 is the latest. So I'll update to the latest but I'm not sure why ReadyAPI already says I'm using the latest. Another bug I guess.
ReadyAPI is very useful but it's riddled with many tiny bugs that apparently aren't high priority enough to get addressed.
Based on threads I've found that are 8 years old and talk about problems that are still problems today, it seems like bugs/enhancements that are deemed low priority don't ever get addressed!
I updated to the latest (2.8.2) and the custom properties are still being overwritten by previous values after a successful run. So the issue is still present where if I rerun a step it will not be re-executing the most recent attempt, it will always be executing based on old data instead of recent data. So frustrating.
The solution smartbear pointed out is to go to the project level and set "Save properties between sessions" to true. I'm not sure why that option isn't available in the preferences section but at least it's not a bug.