Sub : Scripts that are running on developerís machine are not running on test machine. They give an error message saying the object is not being identified.
The application we are working is a Jinitator emulated java applets (which are basically oracle forms). Earlier we have a problem to identify objects. i.e., tables are identified as group of edit boxes. We have tried various alternatives but no success. So we proceeded ahead with edit boxes. We have coded everything and they "are" running properly on the developer's machine. Now we wanted to test the same scripts on different m/c where the QTP started recognizing tables as tables and not edit boxes. As we have used edit boxes (which doesn't exist now), the objects are not being recognized giving an error.
The details of the tool that I am using are as below:
Tool: QTP 9.0 with java add-in 8.2
OS: windows 2000 with IE 6.0
Application: JInitiator 184.108.40.206 emulated Java applets
Below are the verifications that I have checked
1. Checked the version of IE on both m/c and made sure that they are same.
2. Checked the versions of QTP and java add-in are same on both the m/c's.
3. Checked the JInitiator version on both the m/c are same.
Please let me know if any one has inputs. Thanks in advance
Ok, one thing to check is the 'type' of object it is trying to find. Something as trivial as a dropdown list with an actual item count of 6 for example, might have a constant of 1 in the OR so therefore giving you an error....
Also what OS is the developers machine running?... why did you initially develop the scripts on the developer's machine?
I agree - step one is check with the Object Spy to identify Parent and Child attributes - if they are recognized differently than you need to figure out why the environments differ - is it OS, AUT or what?
it tells QTP how many columns should be in an oracle table for it to be identified as a table (instead of a group of edit boxes)
99 is just a number high enough to be sure all tables are identified as tables
The downside of this is bad performance with tables that have a lot of columns (usually 15 columns and above)