| || |
How can i stop the below from happening:
Mr X logs onto windows,starts QTP,
QTP autoconnects to QC using Mr X's credentials.
and now once Mr X logs off and then
Mr Y logs onto windows,starts QTP,
QTP autoconnects to QC using Mr X's credentials.and if you change the credentials to Mr y then he gets logged off from windows.
And then when Mr X logs in and try's to connect to QC using QTP then he would find he is connecting using Mr Y's credentials.
Re: Compliance issue
Why do you want to do auto connect... with different user id?
Re: Compliance issue
We get the same behavior on our test servers (using QTP 9.5 and QC 9.0), where each server supports 5 concurrent user sessions.
This causes problems now that we have 3 large QC projects, and unfortunately each of those Projects has the same folder structure, so that when you start QTP and it auto connects to a QC Project it is always the project that was last explicitly connected to (by you or another user of that PC). We have now placed a named folder at the top of each project's QC tree, so we (hopefully) notice we are in the wrong project--but we are trying to discipline all QTP developers not to use auto connect anymore on the multi-session test servers (but you know how that goes). We are also trying to only work on one QC Project on each of our 3 servers, but a 4th Project is in the pipeline and the client is not going to provide a 4th server.
We have also noticed that whoever last sets the QTP View Options, sets them for all user sessions, while the Search Folder settings are set per user session. Therefore some of QTP's settings apply to an individual session while others apply to the entire PC.
So it appears that while HP/Merc say that QTP will "work" on a multi-session PC, they fail to document just what settings don't "play nice" in that environment.
I conclude this is something you are just going to have to live with if you can't give each QTP developer their own PC (which given the low cost of PCs, seems to be the way to go and the one I would recommend).