Most Esteemed Fellow QTP Users:
For all the joy of seeing my scripts fly in automation after much sweat, this product (QTP) can sure stick a knife in and twist.
QTP seems to "loose" objects that have been recorded in the repository when scripts are run in succession. In other words boot machine run a series of scripts, all is ok. Run them again an buttons found in the first run cannot be seen in the repository. Do an Object Spy, and they are not found in the repository. Do a "record" and QTP is assigning another name to them, generally the something like "browser_1". Totally ####ing with my mind.
Since my LOCAL repository seems to be getting "duplicate" object named under similar object names, I am trying to use the SHARED repository functionality of QTP. I cannot seem to get Update From Local Repository to work. We do not have QUALITY CENTER here. So when I try to link my local to a new shared 'null' repository I have create, it will not let me.
help help help help help
the Confused Mean Man
Re: Repository HELL
1. Use a well developed shared repository
2. Use Descriptive Programing
I test a huge web app with complex Info Path forms included I have lots of dynamic objects but because I use the 2 simple rules above I don't have any issues.