Hi,
This is Balaji. This is a very common scenario when users try to run their scripts remotely or running QTP scripts through QC. You may write a vbs file with a code to send a key repetetively until you close the vbs file.
Ex: you may send NumLock key board input (Using windows shell scripting) continuously to system with some specified time gap and the system will not be locked out.
Thanks,
Balaji Ravi Kumar
Hi,
This is Balaji. This scenario is very common when user tries to run automation scripts on a remote machine or running scripts through a test manager like QC.
To avoid this you may write a vbs file with a code to constatntly send keyboard inputs of a specified key.
Ex: You may send keyboard input NumLock through windows shell scripting and save the code in a vbs file and then execute this before starting QTP. this will run until you close the file and your automation scripts will run without this issue.
Thanks,
Balaji Ravi Kumar
This is Balaji. This is a very common scenario when users try to run their scripts remotely or running QTP scripts through QC. You may write a vbs file with a code to send a key repetetively until you close the vbs file.
Ex: you may send NumLock key board input (Using windows shell scripting) continuously to system with some specified time gap and the system will not be locked out.
Thanks,
Balaji Ravi Kumar
Hi,
This is Balaji. This scenario is very common when user tries to run automation scripts on a remote machine or running scripts through a test manager like QC.
To avoid this you may write a vbs file with a code to constatntly send keyboard inputs of a specified key.
Ex: You may send keyboard input NumLock through windows shell scripting and save the code in a vbs file and then execute this before starting QTP. this will run until you close the file and your automation scripts will run without this issue.
Thanks,
Balaji Ravi Kumar