Forum Discussion

Contributor

6 years ago

Same application on different OS giving different object spy results

Recently we have started to test our application which has always been on 32 bit OS on 64 bit with a 64bit version of the application. However while the majority of the scripts writen originally for ...

RUDOLF_BOTHMA
6 years ago
Hmm, those two mappings aren't even looking at the same properties to identify them. I'm not sure the 64bit property will even manage to find the button correctly. Pointing to just the CLrFullClassName as control probably just brings back one of the child controls. What if your grid contains more than one control ? What if your button is actually an item inside that 64bit control ? That means the 32bit property finds an actual button, but the 64bit one just finds a "control" which is located in the same place, but isn't the actual button. The most likely resolution would be to open object browser for the button in a 32 bit environment and take note of those properties. Then open the same button in the 64 bit environment and take note of that. You will be able to identify something that's almost the same (or with luck identical) eg. NativeClrObject.Name is button10 in 32bit is button10x64 in 64 bit (just examples pulled from thin air) Now, get rid of the 64bit one which is just a control and change the 32 bit one to NativeClrObject.Name "button10*" Your KWTs and scripts can now always refer to that mapped object no matter the OS. TC will be able to figure out what exactly the button is called no matter what OS. Now to your question :

Is it possible TC will do this again ? Yes, definitely. You are always going to have to tweak the mapping properties for your objects. Fortunately once it's done, you shouldn't have to review this unless the developers rename buttons or move them about. Some general things you should consider.

Creating a KWT from recording is a good starting point, but don't rely on it to do your mappings and tests. It's best to turn off automatic mappings and manualy do it before you start recording tests

Manually map items

Turn off

Automatic Mapping

so TC won't create these unwanted objects while you are working.

Vallalarasu_P

Frequent Contributor

6 years ago

Can you share the object browser screenshot for both the bit version.

Can you confirm, The .Net Package installed is same?

Mark1
Contributor
6 years ago

The one with the name map Cash is 32 bit, the other is 64 bit. As you can see its the same button on both applications but one is seen as a button with a ClickButton option and the other is not. I am not sure what you mean by the .Net package.
- RUDOLF_BOTHMA
  Community Hero
  6 years ago
  It looks like you may have to use a wildcard to map/identify the object, so in stead of ...Grid.Border.Grid.Cash make it ...Grid.Border.Grid.Cash*
  
  That should address this specific issue in multiple environments
  
  Or don't link it the the identifier, but use other unique properties that aren't affected by OS in stead
  - Krishna_Kumar
    Contributor
    6 years ago
    Hi Mark1 ,
    
    if the properties are changing for differnt Bit Operating System, try to find the objecs using Regular Expression.
    
    take the part of property values which is same in both the OS and add "*" where ever the needed(Before or After).
    
    in your case the regular expression somewhat look like below code snippet:
    
    assume if the below is the object's propertyname and values of which you are trying to identify : PropNames = "objectIdentifier" PropValue in 32 Bit = "cash" PropValue in 64Bit = "cash64Bit" Sys.Browser("*").Page(*).FindChild("objectIdentifier", "cash*", 10, true)
    
    NOTE: you can use "*" in prefix,suffix and also in between accordingly
    "cash*","*cash","*cash*","ca*h*", etc...