QTP Script not working after upgrade to Siebel 7.7.
I've recently upgraded my Siebel applications from v7.5 to v7.7. I have a QTP script which logs into this Siebel application to check that all pages display within a reasonable timeframe. The script worked for v7.5, but does not work for v7.7.
I get invalid object errors on some objects. If I manually use the object and rerun the script, the error disappears (I think because the page gets cached). It is not feasible to manually do this for all objects and all users in the script every time I want to run the script.
The problematic objects are all links which sit inside Siebel frames. Eg: Browser("Relationship").Page("Relationship").Frame ("Siebel Intelligence").Link("Referred Lending").Click
I used the exist function to check whether the script recognises the problematic objects. It doesn't recognise the frame that the object sits in. I re-recorded my objects and retested. The script still doesn't recognise the frame.
To make sure the problem wasn't just caused by slow page loading, I tried putting wait statements before each object is used by the script. I also put synch statements after each object. This did not work.
Re: QTP Script not working after upgrade to Siebel 7.7.
I don't do Siebel stuff but this problem seems pretty similar to other upgrade issues and it may just come down to a basic identification issue. Unfortunately, from build to build developers may change the way they identify the objects so that when the new version is compiled and old scripts are played against them the identifying attributes no longer match up. Could be the index, could be the name attribute, could be the title, could be the attached text is no longer the attached text but the text, follow? Any way - sounds like you need to investigate using the Object Spy and the Object Repository to see what is different about these links now as compaed to what they were last time (when the descriptions matched). Make a change to the oBject Identification configuration within QTP if need be to get the best configuration. Hopefully you have shared object repositories as you will probably have to go thru and update the OR's. You don't need to change the scripts, just "relearn" the affected objects. Hope that helps.