Ranorex Forum

I have recorded two test cases in Google Chrome, as follows:

1. Open the browser and visit the Google website
2. Search for "Ranorex" in Google.

Both test cases are in a single Test Suite.

The two tests run successfully in Google Chrome.

When I change the browser from "Chrome" to IE, in the first test case, that first test case still runs successfully. However, the second test case (to search for "Ranorex") fails for the reason below:

Failed to find item 'Cross_Browser_TestsRepository.Google.Gbqfq'.
No element found for path '/dom[@domain='[Google URL Removed']//input[#'gbqfq']' within 1m.

How can I fix the second test case so that I can run the test suite (of two test cases), in any browser I want?

Thanks!

p.s. "Google URL Removed" added to the quote above, because I don't have permission to post URLs on this forum.

You are on the right track. First a few questions so we know more about the issue:

What version of Ranorex are you using?

What version of IE are you using?

What version of Chrome are you using?

Have you made sure that the base DOM object (the ".Google" object with the path "/dom[...]") is found in IE manually by selecting Highlight in the repository while ONLY IE is open to the site?
Have you made sure that the path for the search box is found in IE manually by selecting Highlight in the repository while ONLY IE is open to the site?

If the last two questions are answered with "It didn't work" then Ranorex is not finding the objects on the web page for some reason. Use Ranorex Spy and make sure that the IE site matches the XPath.

Thanks for your reply and help krstcs.

krstcs wrote:What version of Ranorex are you using?.....

Ranorex Studio, Version 4.1.5.17134

krstcs wrote:...What version of IE are you using?.....

IE 10.0.9200.16844

krstcs wrote:What version of Chrome are you using?.....

Chrome Version Version 33.0.1750.154 m

krstcs wrote:...Have you made sure that the base DOM object (the ".Google" object with the path "/dom[...]") is found in IE manually by selecting Highlight in the repository while ONLY IE is open to the site?
Have you made sure that the path for the search box is found in IE manually by selecting Highlight in the repository while ONLY IE is open to the site?...

I haven't done that. What I did was record the tests in Chrome and then expected them to run in IE. Is that not possible?

Thanks again!

Some times it is possible, some times it is not.

Each browser engine presents the HTML a little bit differently, so we need to make sure that it works in each one, we can't just assume that it will. This is something that I've learned the hard way.

But, once you know that there are differences, and where they may be, you can typically create the object RXPaths in a way that will work for any of them.

I typically create objects with all the browsers that I need to test in open, so I TRACK and ADD the item to the repository from one and then make sure it matches the others. It does take a few more minutes, but once you get it done, unless the devs change things, it should work from then on.

Remember, automation is not necessarily faster than manual testing in creating tests (and usually it is much slower). Where automation shines is in running and re-running and re-re-running tests. It will do it faster than a human and exactly the same way every time so we don't have to worry about humans messing up a step and having to waste time going back. It is also much better at reporting once it is set up.

Now, once you do have a framework in place that works for you, adding new test cases will be much simpler, but it takes some time to get there.

Thanks again for your helpful reply krstcs.

krstcs wrote:...I typically create objects with all the browsers that I need to test in open, so I TRACK and ADD the item to the repository from one and then make sure it matches the others...

Where can I learn more about how to do that?

Simply go to the repository editor, here click the "Track" button and then select the element you want to compare with the other element tracked in other browser. The selected object is then added to repository. Then repeat the same steps with each web browser you would like to support.

There could happen two things:
- In case the element has the same path as an already added repository element, no new repository element is added. Hence, both web browsers interpret the HTML code the same way.

- In case the other web browser interprets the HTML code differently, Ranorex detects different path and adds a new repo element with different path. In this case, you need to compare both paths and try to make either of them recognizable by both web browsers.

You can for example replace some path elements with somewhat more generic elements, using "?" character, "*" adapter or relationship operators. All these things you can find described for example here:
http://www.ranorex.com/support/user-gui ... xpath.html
and here:
http://www.ranorex.com/support/user-gui ... ditor.html

These two articles are in my opinion crucial to learn and understand, to be able to effectively work with the xpaths.

Yep, what odklizec said.

Reading the user guide from top to bottom is one of the primary things that you will find helpful when learning Ranorex. They created a really nice document that will help answer a lot of your questions.

And the RanoreXPath technology is something that you will want to learn inside-out as it is the core of how Ranorex finds and identifies objects. It is very powerful.

Thanks everyone for your helpful replies and suggestions. I will spend some time learning more about RanoreXPath and Ranorex Spy.