Ask a Question

Cross Browser Testing / NameMapping issues

Frequent Contributor

Cross Browser Testing / NameMapping issues

Good afternoon everybody...  I have a fairly extensive suite of keyword tests I created for IE that are finally running really well after a lot of learning (many thanks to you all in this forum!).  I have gotten to the point where I am ready to execute these in other browsers.  After attempting to run the tests in Chrome, I am running into instances where objects are not found in the NameMapping file, which is bringing the test to a halt.  I assumed the mapping would translate seamlessly, I guess.  Silly me. 


I know I can add "If Browser..." logic into my tests, and map all of the fields in the other browsers, but I was wondering if there was a better way?  There are several hundred objects to map and the namemapping file is unruly enough as it is.  I would much rather recreate the tests in a whole new suite with a whole new NameMapping file to run against Chrome, which may be my best option at this point.  Just wanted to see what some of you more experienced folks think. 


Going forward, is there a better way of creating tests to run across multiple browsers?  What should I do differently next time? 




Community Hero

This might be of some help:

[Community Hero]
[Community Heroes] are not employed by SmartBear Software but
are just volunteers who have some experience with the tools by SmartBear Software
and a desire to help others. Posts made by [Community Heroes]
may differ from the official policies of SmartBear Software and should be treated
as the own private opinion of their authors and under no circumstances as an
official answer from SmartBear Software.
The [Community Hero] signature is used with permission by SmartBear Software.
Community Hero

Creating the tests in separate projects for multiple browsers would not be a good idea. If you need to update your test for any new functionality you now have to do it twice. 


I have found that opposed to using name mapping for web testing, that Find methods (FindChild, FindChildEx, FindAllChildren) etc.. are much more reliable. Also, consider building a framework doing any non-verification steps as opposed to re-recording / writing those actions for each individual tests. Things like logging in or page navigation. Doing this will make maintenance of the tests A LOT easier. 


Click the Accept as Solution button if my answer has helped

Whats getting broken in your mapping properties?


I've used mapped objects cross-browser without any trouble? I've also used helper/finder functions (such as suggested above).


I found way more inconsistency in how the CSS layer translates between different browsers than I did with mapping properties.

Showing results for 
Search instead for 
Did you mean: