I have a strong hunch this is going to be "stupid pilot error", but I am really stuck trying to get 3 complex tests ready for a demo later today--and my west coast team members (I am working remote in EST time zone). So any feedback that you can quickly provide will be much appreciated.
-Thanks, Terry Horwath
Using QTP 9.5 and QC 9.0
For the last several weeks I have been developing QTP tests, resident in QC. But None of these tests have been sharing or calling shared Actions.
Today I created the first "shared Action" test and saved it to our shared Actions folder.
I go through all the [correct in the past] steps using the Insert Call to Existing Action dialog, when I press OK (or whatever) it silently closes the dialog (no errors or exceptions), but does NOT insert the Action in my testcase.
I have created a few variations of test scripts with named as well as unnamed shared Actions and the results as described above are always the same.
Is this a permission thing in QC?
Has anyone encountered this? And if so, what is the "stupid" thing I am doing, or that is different in this respect working QTP standalone versus QTP integrated with QC?
P.S. And while I have been doing battle with QC-isms (what a heavy weight wrapper!) I have up until now felt that I have a proper integration between QTP and QC--so no other gotchas encountered.
Re: can\'t insert a call to an existing shared Acti
Well, this turns out to be a bug with QTP/QC integration. Two of us on our team confirmed the following behaviors:
1. If QTP is working with tests and shared Actions in the file system, and not connected to QC, you <u>can</u> use the full path option (i.e. you say "no" to the irritating "do you want to add path blah to the Folders list..."?) and successfully insert the call to the shared action in the calling test.
2. But when QTP is connected to QC, and is using QC shared Actions, you can <u>not</u> use the full path option when inserting a shared action--you <u>must</u> use the (supposedly optional) path-relative method when inserted the shared action.
This is a major bug--either in QC or QTP--because the QTP relative path Folder setting and dialog lives under the QTP Tools->Options... menu, as as such settings on this menu exist in the context of QTP <u>Windows login session</u>--and do not follow the test in which you answered "yes" to using the relative path.
In our client's environment we have 4 servers, each with 5 virtual user sessions--so we are going to have to write a vbScript with QTP AOM directives to set this path in the relative Folders setting in each session (and we are going to have to do this anytime we introduce a new QC/QTP project, as each will have their own shared Actions folder in their unique QC project).
This behavior was easy to reproduce, so I am wondering if anyone else has experienced it. Another senior QTP engineer sat with me (well in a connected desktop session) and first watched me perform these steps, and then he did it himself, so I am convinced this is a real problem.
I would sure appreciated any feedback from anyone out there using QTP 9.2 and QC 9.0, as well as those using QTP 9.5 and QC 9.0 on this behavior.
P.S. We are going to try and log this issue with HP/Merc, but we have to work through the client and it can ofter take a lot of time.