Missing Resources QTP
I am experiencing weird behaviour from QTP.
I have Test ABC in which I added reusable actions of Test XYZ using "Insert Existing Action".
Now The physical location of Test XYZ was X Drive.
Now I have moved TEST XYZ to other Physical location say some shared drive.
Now when i open Test Abc QTP shows me all reusable actions of XYZ as missing resources which is right since the test is moved physically to shared rive.
So I using locate and then providing path of new location of test xyz i try to map one of the reusable action.
It rightly identifies the action from the Test XYZ and shows in that dialog. When i click Ok and QTP maps/replaces this action in Test ABC by some other random action :O . and it uses this same random action for all mappings
Test ABC : Action 1 is missing
Locate, Browse and provide new location of TEST XYZ for mapping
It finds Action1 in XYZ and maps correctly in locate dialog
Click on OK.
In Test Flow QTP replaced Action1 by Action R and not Action1
If repeat same steps for Action 2 it also replaces by same Action R
Its not possible for me to delete all reusable actions and add them again because they are lot.
Can anyone help me in locating and mapping all actions correctly.
Is this QTP 11? Or is this UFT 11.5?
I am using UFT 11.5 and integrating with ALM 11. There are a *lot* of serious issues with the integration of UFT and ALM revolving around adding and removing reusable actions when ALM is involved. In a nutshell, if you are still connected to ALM when you try to remove a call to a reusable action stored in ALM, the reusable action *appears* to be deleted. However, if you close and re-open the test that calls that action, the action is still there. Until you break the connection with ALM, the action can't be deleted from the test (that is, you still see it in View/Solution Explorer even though the call to the reusable action is gone from Test Flow and from the code. HP is working this issue right now as a Critical. I've done WebEx's and sent them exports of scripts and ALM project backups. This has been going on for almost 5 weeks now without resolution. Further, if this issue goes undetected (i.e. the "orphaned" reusable action), the script can get further corrupted to the point where no changes can be made, making maintenance impossible and the only recourse is to redevelop the script virtually from scratch. My opinion: the UFT - ALM integration is very buggy and was not ready for the field.
Is it difficult to create a Network Drive with the same Name & recreate the path in some way? That would be easy way.
Originally Posted by rajrkodeep
Alternately, you can try this post. But that involves deleting & re-inserting the calls.