A small team for 4 of us are developing tests against windows and ios applications with Windows 7 and Ranorex 4.1.1. We have found that after some time the changes made to a recoding module are not saved to disk, they appear to be held in memory and the module will execute when run within Ranorex. But as soon as the Ranorex IDE is closed the changes are lost. This can also be observed when attempting to commit changes to version control with the IDE still open and the file diffs show that not all of the changes are present in the file.
All four of us have experienced this problem but I haven't seen anyone else mention it on the forum, so would be interested to hear if anyone else is seeing this. Is it a known issue?
Our current workaround if we notice this happening is to save the recording module as a separate file, then restart Ranorex and copy the contents back into the original recording module.
Ask general questions here.
3 posts • Page 1 of 1
Would it be possible to upgrade to Ranorex 4.1.2 and try it again on one machine? We have a few known issues with Source Control and the Ranorex Views and we are currently investigating this issues. Those issues should be fixed in one of the upcoming versions of Ranorex, we already fixed a few with Ranorex 4.1.2.caleb wrote:All four of us have experienced this problem but I haven't seen anyone else mention it on the forum, so would be interested to hear if anyone else is seeing this. Is it a known issue?
Thank you, we have upgraded our team to 4.1.2 and my impression after one day is that stability seems to have improved. There are still some quirks around saving occasionally but it's happening far less often. If we get reliable steps to reproduce anything I will let you know.