Page 1 of 1

Identifies objects at end of timeout

Posted: Mon Aug 10, 2015 5:22 pm
by ollie99
I am running Ranorex 5.4.
When running the tests for some reason it only picks up objects and clicks on them after the search timeout has ended, and this makes the whole testing process not work so well, causing errors or making a test take a long time to run.
Is there a way of fixing this?
Thanks.

Re: Identifies objects at end of timeout

Posted: Mon Aug 10, 2015 5:38 pm
by krstcs
Can you post an example test solution that demonstrates the issue?

Also, please give us more information, including the following (which should always be included when raising issues on the forums):

Windows version
Technology of system-under-test (SUT) (Java, Flash/Flex, WPF, HTML, etc.)
RanoreXPath of the elements in question
Ranorex Snapshot (not a screenshot) of the elements in question
Full text of any error messages


My guess would be that you don't have something in the XPath set correctly for the elements you are looking for, potentially the root element's RXPath, which is why it is taking too long to be found. You should make the RXPath as specific as possible. The more generic it is, the longer it will take for Ranorex to find the matching item. Also, consider using unique ids, which are much faster (your developers will need to include them in the SUT's code-base, but they should be doing that already).

Re: Identifies objects at end of timeout

Posted: Tue Aug 11, 2015 10:44 am
by ollie99
I am using a remote desktop to a virtual server of which the OS is Microsoft Windows Server 2008 R2 Standard.
I think the technology of the system is WPF.
It is not one specific element, a few seem to be okay but, as I said, most are only clicked on after the search timeout has ended.
When opening ranorex spy this warning is shown:

"You are accessing WPF elements via the UIA plug-in. UI element identification capabilities for this window are limited. Consider using the native WPF plug-in."
I am not sure how to configure the settings for that.

Attached is the snapshot of the main window of the program and also the report of a test.
As you can see in the reports, there are a lot of warnings along the lines of:

"Item 'PACEtestsRepository.MainWindow.Image' could be found using its absolute path, but not using its relative path from the cached element of parent folder 'PACEtestsRepository.MainWindow'. This can happen if either the item search timeout is too small or if items within a rooted folder do not share a common parent element. To fix this problem, first increase the item search timeout. If this does not help, create a separate rooted folder for this item or disable caching for the specified folder."

Thanks

Re: Identifies objects at end of timeout

Posted: Tue Aug 11, 2015 1:36 pm
by krstcs
So, if you read the errors, there are two issues you need to address.

First, you need to make sure that the WPF settings in Ranorex are correct, that's what the technology limitation warning is about. I don't test on WPF so I can't help there.

Second, the path to the elements has a problem. Make sure that the path is correct, and specific, for each element and for the root and each folder.

It could also be that the first issue is causing the second issue.

Re: Identifies objects at end of timeout

Posted: Tue Aug 11, 2015 2:08 pm
by ollie99
How do I make sure that the path is correct and specific?

Re: Identifies objects at end of timeout

Posted: Tue Aug 11, 2015 2:37 pm
by krstcs
You will need to use Ranorex Spy.

Have you read the user guide? I highly recommend it, as it explains all of this in detail.

http://www.ranorex.com/support/user-guide-20.html