The Online Help and the vuGen PDF user's manual both only describe <u>how</u> you import an Action from one test script to another. But what is meant by "importing"?
1. Is this simply a copy operation of Action1 in TestX into TestY? OR
2. Is this a logical linking of Action1 into TestY? If it is a logical linking, can I edit Action1 once it is imported to TestY, or is it in a read-only state (this is the model that QTP uses when importing shared Actions).
Any other gothchas or things I should know if I plan to import Actions?
You are literally copying the action of another script and its resources into the same script folder, code, parameters, snapshots, etc. The context in which I use this most frequently is when the login code is the same in one script and correlation is inolved, and - it applies to the current script beign enhanced.
For me, I rarely worry about the snapshots anyway, so copy and paste, combined with looking at log output, works just as well as import. Now, if this turned as some point into a link to a library, well that would be different.