im not sure what you mean by External Actions, but yes we use Actions in nearly every script -- an action to take care of optional screens, another action when a login is required, occasional actions to go out and get a set of screen data, etc...
By External actions i mean a reusable Action stored in a different test and being called in your test. People have reported that they get missing Actions in test when such a setup is there and the upgrade is done
Is there a link to an issue on this somewhere? I have a support ticket currently into HP on this as we are experiencing something similar when we upgraded QC to v10. HP so far has not acknowledged the issue as an existing one.
We already did the QTP upgrade to 10 and that was working fine under QC 9.2. Seems a little whacky that the issue is happening with version 10 QTP tests.
One issue that affected my scripts after the upgrade from 9.5 was the presence of TO-HWND and Native HWND for the Browser object. This can be viewed by spying the Browser object and viewing the HWND properties on the TO and Native sides - they will both be different. Its a quick fix, but, I wouldn't have expected this behavior to begin with.
I will keep chasing this down with HP support. I am still wondering if this has something to do with our clustering. We have two QC servers and using Big IP to load balance them. I think I might need to turn on persistance on both.
Anshoo - Not seeing that problem (At least not yet).