Hi,
thanks for the two great tips. I never selected more than one line to convert them to user code, so I never saw the merge command before.
And image test moving to another method is now also working.
Thanks.
Have a nice weekend.
Search found 14 matches
- Fri Nov 25, 2016 9:25 am
- Forum: Bug Reports
- Topic: Image validation user code issue
- Replies: 4
- Views: 2751
- Wed Nov 23, 2016 12:23 pm
- Forum: Bug Reports
- Topic: Image validation user code issue
- Replies: 4
- Views: 2751
Image validation user code issue
Hello, STR : * Add a new test case * Add a new Recording Module in this test case * Click at "Record" * Do an action of your choice, for example a simple mouse click * Add an image base screenshot validation * Stop the recording * Convert both commands to user code * Test it Independent if the tests...
- Mon Sep 19, 2016 1:43 pm
- Forum: Bug Reports
- Topic: Host.Local.FindSingle hangs if search process in dead lock
- Replies: 8
- Views: 2050
Re: Host.Local.FindSingle hangs if search process in dead lock
Yes,
they have had access to my computer several weeks ago via Teamviewer and they have make some loggings.
Since then they have released V6.1 but I can't see a solution for this problem in the release notest.
they have had access to my computer several weeks ago via Teamviewer and they have make some loggings.
Since then they have released V6.1 but I can't see a solution for this problem in the release notest.
- Fri Sep 16, 2016 8:18 am
- Forum: Bug Reports
- Topic: Host.Local.FindSingle hangs if search process in dead lock
- Replies: 8
- Views: 2050
Re: Host.Local.FindSingle hangs if search process in dead lock
Hello,
do you have find the problem and any solution for it ?
Thx
Stefan Plümper
do you have find the problem and any solution for it ?
Thx
Stefan Plümper
- Mon Aug 29, 2016 10:06 am
- Forum: Bug Reports
- Topic: "Open report after execution" does not work
- Replies: 53
- Views: 13772
Re: "Open report after execution" does not work
Annotation: the generated reports are not listed at the Projects list at Windows 10, in opposite to Windows 7
- Mon Aug 29, 2016 9:47 am
- Forum: Bug Reports
- Topic: "Open report after execution" does not work
- Replies: 53
- Views: 13772
Re: "Open report after execution" does not work
Hello,
I have tested it with a small new solution and there it works.
It is possible that this is a problem from copying the solution under Windows 7 to Windows 10 without any modifications ?
I have tested it with a small new solution and there it works.
It is possible that this is a problem from copying the solution under Windows 7 to Windows 10 without any modifications ?
- Thu Aug 18, 2016 3:30 pm
- Forum: Bug Reports
- Topic: "Open report after execution" does not work
- Replies: 53
- Views: 13772
Re: "Open report after execution" does not work
Hello, I have installed a test version of the Ranorex Studio 6.0.2 in a VMWare Player 12.1.1 with Windows 10 1607. At my real test PC (running with Windows 7 SP1) the report opens after finishing the test, but in the VM it have to be open manually. I deleted the "C:\Users\YOUR_USER_NAME\AppData\Roam...
- Tue Jul 12, 2016 12:11 pm
- Forum: Bug Reports
- Topic: Host.Local.FindSingle hangs if search process in dead lock
- Replies: 8
- Views: 2050
Re: Host.Local.FindSingle hangs if search process in dead lock
Additional info:
I'm using Ranorex 6.0.1
I'm using Ranorex 6.0.1
- Tue Jul 12, 2016 10:19 am
- Forum: Bug Reports
- Topic: Host.Local.FindSingle hangs if search process in dead lock
- Replies: 8
- Views: 2050
Host.Local.FindSingle hangs if search process in dead lock
Hello, I have a test where I exit our application. Unfortunaly due to a failure in our KDE implementation the process don't exit but remain in a dead lock issue, so the process is still existing. My problem is that the Host.Local.FindSingle method never throw an exception if the duration time is exp...
- Mon Jun 13, 2016 7:41 am
- Forum: Bug Reports
- Topic: Ranorex 6.0 stops at Delay.Milliseconds(200)
- Replies: 6
- Views: 2620
Re: Ranorex 6.0 stops at Delay.Milliseconds(200)
Hello,
I have written 'FindElement' by myself, and have done a failure at the exception handling.
I don't know how that helps you...
I have written 'FindElement' by myself, and have done a failure at the exception handling.
I don't know how that helps you...
- Tue Jun 07, 2016 3:58 pm
- Forum: Bug Reports
- Topic: Ranorex 6.0 stops at Delay.Milliseconds(200)
- Replies: 6
- Views: 2620
Re: Ranorex 6.0 stops at Delay.Milliseconds(200)
Hi, there are two messages, both with "Examin tree", the first with text Search tree '/form.... (before the Delay) and after the delay and the initialization of itemO, a line Search tree item '/form... is missing, directly before the second try command. I don't believe that the script stops at first...
- Tue Jun 07, 2016 11:31 am
- Forum: Bug Reports
- Topic: Ranorex 6.0 stops at Delay.Milliseconds(200)
- Replies: 6
- Views: 2620
Re: Ranorex 6.0 stops at Delay.Milliseconds(200)
Hi,
I tested it and yes, it seems to be the FindElement. But why the Report.Log line before the try, after the Delay, is not visible at output ?
That was the reason for me to believe it was the Delay line...
I tested it and yes, it seems to be the FindElement. But why the Report.Log line before the try, after the Delay, is not visible at output ?
That was the reason for me to believe it was the Delay line...
- Thu Jun 02, 2016 8:39 am
- Forum: Bug Reports
- Topic: [Ranorex 5.4] Failed to instrument WPF process.
- Replies: 6
- Views: 2887
Re: [Ranorex 5.4] Failed to instrument WPF process.
Hello, now I get the error at 6.0 again. I have tried your solution for this, setting "WPF Legacy/UIA Interaction" to "WpfOnly", but the message occurs every start. And I don't know what you mean with "WpfElement" window at Spy, there is no such window - it is a Qt5 application, could that be the pr...
- Thu Jun 02, 2016 7:46 am
- Forum: Bug Reports
- Topic: Ranorex 6.0 stops at Delay.Milliseconds(200)
- Replies: 6
- Views: 2620
Ranorex 6.0 stops at Delay.Milliseconds(200)
Hello, I have installed Ranorex 6.0 3 days ago and now I have the problem that it freeze obviously at a Delay.Milliseconds command. At the attachment you see at right top the "Waiting for 200 ms", at the left bottom console that the previous command was started at 08:22:20 and the right bottom clock...