Ranorex Forum

Hi,

I have the same textbox being referred to (from repository) in separate recordings each under separate test cases. The first recording under the first test case Ranorex can peform a key sequence in the text box. Whereas in the 2nd recording module under the 2nd test case the key sequence doesn't work, even though the report indicates everything ran ok.

My repository items have been grouped under a simple folder.

Why isn't this working?

Hi,

Are you using a module variable to input the key sequence, maybe you forgot to bind the variable in the second test case?
Can you send us the report file and the two recording files?

Regards,
Markus
Ranorex Support Team

Have attached the two recordings and the report.

Also was not using variables ... just static text.

Also ... the failure in the report has nothing to do with the key sequence not working.

Also note ... the spelling checker recording is working and the create other event is not.

On further inspection ... both the recording files work fine when run in isolation. The problem occurs when I run the "NewNotification" recording just before the CreateOtherEvent recording. "NewNotification" just creates a new instance of the form.

Have attached it as well.

Hi,

Could it be that the RxPath changed after you have performed the click on the "New" Button?
Please check with the Ranorex Spy tool if the paths change or if you are able to manually inbut the key sequence to the specific textbox after that click?
Would it be possible to create two Ranorex Snapshot files of the specific textbox, one before you click on the "New Button" and one after that click?
Following link will show you how to generate a snapshot file:
http://www.ranorex.com/support/user-gui ... files.html
By the way please update to the Ranorex 3.2.1 version, here is the link.
Whenever a new Ranorex version is released, you will get an email pointing you to the downloads for the newest version.

Thanks in advance!

Regards,
Markus
Ranorex Support Team

This was a bug with our software that has been fixed, and has resolved this issue.

Thank you for the feedback!

Regards,
Alex
Ranorex Team