I am trying to determine if I am not understanding rights within QTP or if this is a problem with my rights on the VM QTP is installed on, or possibly somehow the setup of QTP.
Even on a new test I create (saved or unsaved), file.Close always unavailable. I can open another test and that seems to close the test, but through Explorer I still see the lock.lck file in the test. I expected to be able to use the File.Close command and also that there would not be a lock.lck file after I had opened a new test (essentially closing the first test).
That doesnt bother me so much, but sometimes I seem to have trouble with an object repository file or function library being uneditable- then I have to "Save As" instead of "Save" ...and then update my driver script pointing to those resources. That is more bothersome, but less reproducible. I thought this might be related to the inability to close my tests.
QTP 11 is installed with concurrent license- client is being run on one virtual machine and license server is on another VM in a VMWare environment. there is no problem with the connection.
i have admin rights on the VM with QTP running on it.
About the new test I created- there are no associated function libraries and it has only a local object repository.
No one else is logged into the VM. I have tried shutting down QTP and reopening- still File.Close is disabled.
I am getting back to QTP after quite some time, so this might be a simple thing, but I am not finding info , so any help would be appreciated. thanks.
According to the Help documentation (which concurs with my experience with QTP v11) the File > Close option applies only to Function Libraries. Here's the path through the Help document to the relevant section.
HP QuickTest Professional User Guide > Introducing QuickTest Professional > QuickTest at a Glance > QuickTest Commands > File Menu
The only way I have observed that a Test can be closed is by opening another Test.
Regarding the "uneditable" state of a Function Library or Object Repository, the question to first answer is how did you get the file opened to begin with? Did you open it in a manner that it would be editable? Note also with object repositories stored in QC, you can't overlay an existing entity (object repository or function library) with a new entity created from scratch. You have to open the original entity and edit it and save it back to itself. You can't start a new entity from scratch and then save it in QC using the name of an existing entity with the intent of overwriting the existing entity.
(Opinions and information contained in this post are wholly my own and do not reflect the opinions of my employer.)
Trudy - Thanks for your response- I was finding some of that help yesterday, but I also appreciate the confirmation. Here is a recap in case anyone goes looking for this type of info- see if I get this right:
I dont use QC so htere may be some added considerations involving QC
Tests- you only can have 1 open and you dont have to explicitly close it for function libraries or ORs to be editable. The Lock.lck files you see via the file system can be deleted unless you have a file open, but their presence doesnt automatically mean a file is locked.
Function libraries- if you are finding they arent editable- make sure no one else is accessing them and also that you are not running/debugging the test.
ORs- If you open up a shared OR- it will be uneditable until you select File.Enable Editing.