class is changed in webtable
I'm testing one web application, Grid previously it was identified as WPFGRID class name we written in code every part as
but It's identifying as WBFGRID
now we have to change in every part of the code is there any solutions for this .why it's identifying differently.
how to solve this.
Everytime we are loading .net addins correctly
It's ween a while since I used QTP. Most tools support of idea of Mapping, and aliasing.
The idea is you map things in an object map, then you alias those objects when you reference them in a script. So when an object changes, you remap that object, but point your alias at the new object. This will give you a single point of maintenance for all object properties.
Same as above suggestion but a bit coding perspective...
Set objGrid = Browser(B).page(p).wpfgrid(x)
Whenever the grid object changes you can modify the name of the object at object creation level will reflect everywhere it is invoked.
An idea that I have used in the past was to use descriptive programming in libraries. Then I used replace string (Ctrl + h) in the editor to globally change when descrptions change.
I don't recommend this. But I have worked like this when I used existing code.
If the properties are in the OR, I'd guess it would take a long time to locate and change each object. Maybe you could export to an XML file, do the replaces and import again. I have not tried this, but I think it would work.
Descriptive programing is good for deep object trees. Mapping is suppose to help with a lot of the ID changes where changes tend to be in ID numbers, and element properties.
Where descriptive programming is very helpful is when changes cause elements to move up and down levels on the hierarchy tree. With descriptive programming you can do deep find operations on nodes, and assign your elements relatively to say a parent frame/page that's further up the chain. This tends to be more reliable.
Most record and playback will default to using absolute pathing because it's far faster. Native application automation tools don't perform well with deep find operations since they have to scan all the UI objects on the screen. That's why they are less used.
The most commonly used middle ground is to first map the objects automatically, then assign those mapped object aliases that can be used in script code. When the objects change, you just remap everything, then point the aliases to their new mapped properties.