QTP 8.2 (Java Add-in): Object naming strategy
I've been playing around QTP 8.2 (Java Add-in) to test a Java application.
I have noticed that QTP uses it's own naming convention when identifying JavaTables. I'm not sure why, but JavaButtons seems to be identified fairly well.
My question is about identifying Java objects in QTP. What object properties in a Java Table should be filled in to allow QTP to identify multiple tables in a single frame?
I've used the Spy Object tool to get to the properties of a JavaTable and I can see that the attached text is not filled in. Is this an important property to fill out?
I want to make sure that Java objects can be uniquely identified accross new versions of the software. If a 3rd JavaTable is added to a frame, I want to make sure that my QTP tests don't fail because they pick up the wrong JavaTable.
I also want to tell the developers what object properties to fill in for JavaTables, JavaButtons, JavaCheckBoxes, etc.
Re: QTP 8.2 (Java Add-in): Object naming strategy
Well, I'll answer my own questions! In QTP 8.2, you can open the Tools -> Object Identifier... window.
This window allows you to select the
"Environment" e.g., Java, Web, or Standard. If I select "Java", then I get a list of Test Object Classes.
I can select "Java Table" and modify the "Mandatory" or "Assistive" object properties used in identifying the Java Table.
The default assitive properties were "toolkit class" and "attached text"
I'll play around some more...