Hi Omkar,
I Would like to bring to your notice that QTP may not replay consistantly on a locked machine.
Quick Test Professional 9.5:
When running Quick Test on a remote machine using a Remote Desktop Connection session (RDC) or using Citrix, if the remote session is minimized during the run session, or if the computer on which the application is being tested is logged off or locked, the following problems may occur:
• The test or component run session may fail
• steps that contain keyboard or focus operations may fail
• The Test Results still image capture and/or the Screen Recorder may display a black screen steps for which the device level replay is configured to use the mouse (instead of browser events) to run mouse operations may fail. (You set the device level replay using a Setting.WebPackage ("ReplayType") statement or by setting the Replay type option in the Advanced Web Options dialog box.)
Workaround: If you are using Citrix or a Remote Desktop Connection session to run a test or component, do not minimize the session window, and make sure that the computer on which the application is being tested is not logged off or locked.
Quick Test Professional 9.2:
When attempting to run a test from MDRV/Quality Center on a computer with an incompatible execution environment (such as a locked computer), Quick Test Professional 9.2 will not run the test and displays one of the following error messages:
The Quick Test Professional computer is locked or logged off.
Quick Test Professional was launched without permission to interact with the desktop.
The following registry key which enables you to run tests on a remote computer, even on an incompatible execution environment:
HKEY_CURRENT_USER\Software\Mercury Interactive\Quick Test Professional\MicTest\SkipEnvironmentChecks
Set the registry key to 1 to prevent the remote execution checks, and 0 to perform the checks.
Important note:
Note that tests may fail when run on a computer with incompatible execution environment. For more information, refer to the Non-version specific information section below.
Quick Test Professional 9.1:
When attempting to run a test from MDRV/Quality Center on a computer with an incompatible execution environment (such as a locked computer), Quick Test Professional 9.1 will not run the test and displays one of the following error messages:
-> The Quick Test Professional computer is locked or logged off.
-> Quick Test Professional was launched without permission to interact with the desktop.
Private patch QTP91P1602 (Add registry key to prevent remote execution environment checks) addresses this problem. This patch adds the following registry key which enables you to run tests on a remote computer, even on an incompatible execution environment:
HKEY_CURRENT_USER\Software\Mercury Interactive\Quick Test Professional\MicTest\SkipEnvironmentChecks
Set the registry key to 1 to prevent the remote execution checks, and 0 to perform the checks.
Important note:
Tests may fail when run on a computer with incompatible execution environment.
Finally I would rather suggest you to have a isolated-secured Test lab for scheduled script Execution thereby preventing the PC Locks.
I Would like to bring to your notice that QTP may not replay consistantly on a locked machine.
Quick Test Professional 9.5:
When running Quick Test on a remote machine using a Remote Desktop Connection session (RDC) or using Citrix, if the remote session is minimized during the run session, or if the computer on which the application is being tested is logged off or locked, the following problems may occur:
• The test or component run session may fail
• steps that contain keyboard or focus operations may fail
• The Test Results still image capture and/or the Screen Recorder may display a black screen steps for which the device level replay is configured to use the mouse (instead of browser events) to run mouse operations may fail. (You set the device level replay using a Setting.WebPackage ("ReplayType") statement or by setting the Replay type option in the Advanced Web Options dialog box.)
Workaround: If you are using Citrix or a Remote Desktop Connection session to run a test or component, do not minimize the session window, and make sure that the computer on which the application is being tested is not logged off or locked.
Quick Test Professional 9.2:
When attempting to run a test from MDRV/Quality Center on a computer with an incompatible execution environment (such as a locked computer), Quick Test Professional 9.2 will not run the test and displays one of the following error messages:
The Quick Test Professional computer is locked or logged off.
Quick Test Professional was launched without permission to interact with the desktop.
The following registry key which enables you to run tests on a remote computer, even on an incompatible execution environment:
HKEY_CURRENT_USER\Software\Mercury Interactive\Quick Test Professional\MicTest\SkipEnvironmentChecks
Set the registry key to 1 to prevent the remote execution checks, and 0 to perform the checks.
Important note:
Note that tests may fail when run on a computer with incompatible execution environment. For more information, refer to the Non-version specific information section below.
Quick Test Professional 9.1:
When attempting to run a test from MDRV/Quality Center on a computer with an incompatible execution environment (such as a locked computer), Quick Test Professional 9.1 will not run the test and displays one of the following error messages:
-> The Quick Test Professional computer is locked or logged off.
-> Quick Test Professional was launched without permission to interact with the desktop.
Private patch QTP91P1602 (Add registry key to prevent remote execution environment checks) addresses this problem. This patch adds the following registry key which enables you to run tests on a remote computer, even on an incompatible execution environment:
HKEY_CURRENT_USER\Software\Mercury Interactive\Quick Test Professional\MicTest\SkipEnvironmentChecks
Set the registry key to 1 to prevent the remote execution checks, and 0 to perform the checks.
Important note:
Tests may fail when run on a computer with incompatible execution environment.
Finally I would rather suggest you to have a isolated-secured Test lab for scheduled script Execution thereby preventing the PC Locks.