Skip to main content

Handling auto populate, delayed masking and auto select fields

While doing automation, we could have come across the fields which will do the functionality like,
1. While entering some text, it will auto populate the matching values
2. While entering the text, it will mask the values i.e. convert to xxx.. or ....

To simulate the functionality many of us could have faced problems while entering the values on the field;

  • The value entered is not converting as masking text as it is doing while manual flow
  • The form not accepting the entered values
  • The entered/selected value not persists in the field after the simulation, etc.

How to handle such controls effectively. Here we go;
1. WScript.Sendkeys

Set shell = CreateObject("Script.Shell")
Window("hwnd:=" & Browser("myApp").GetROProperty("hwnd")).Activate  'if it's Browser
obj.Set ""
Wait 1
obj.FireEvent "OnFocus"
Wait 1   
shell.SendKeys "your value", 1000
Wait 1
shell.SendKeys "{TAB}"

The important thing here, always have focus on the current window before passing sendkeys.

 You can call the blur event after entering the values in the field like;

Set shell = CreateObject("Script.Shell")
Window("hwnd:=" & Browser("myApp").GetROProperty("hwnd")).Activate  'if it's Browser
obj.Set ""
Wait 1
obj.FireEvent "OnFocus"
Wait 1   
shell.SendKeys "your value", 1000
Wait 1
obj.Object.blur 'OR obj.FireEvent "OnBlur"

May be both the approaches will fail or should be better approaches out there, please feel free to share with us.


  1. Thanks for sharing great information in your blog. Got to learn new things from your Blog . It was very nice blog to learn about Selenium

  2. Hi I need a help with RESTAPI testing UFT 12.53, where I have to take a response json and make it as an input to another HttpRequest or store it in the file as a step output. Can you please give me what steps I might need to follow. I did go through this : but somehow not able create the file.


Post a Comment

Popular posts from this blog

QTP - Object Identification - Prerequesties

While starting a new project or proof of concept or after new QTP installation, we would face the issue in identifying objects as QTP built objects like WinList, WebEdit, etc.; instead everything will be identified as WinObject.

Here are some steps to ensure you did the environment setup RIGHT before start automating.
Did you enabled required Add-ins only while launchingDid you selected "Record >> Record and Run Settings" - This should be based on what type of application you are working with
Windows app - Windows >> Record and run test on any windows applications. Web app - Web >> Record and run test on any open browser.
Did you tried to launch UFT/QTP and then AUT.If its web, ensure browser zoom level set to 100%Try disabling the protected mode in IE for web.Launch UFT and AUT using RUN AS ADMINISTRATORAlso see the Object Identification Methods if you are interested.

Change IE Browser ZOOM settings

Lot of UI automation testers could have faced this problem as we could change the zoom settings while operating manually for our convenience and forgot to reset to 100%.
But our QTP and some other related tools would operate the browser perfectly if browser zoom is 100%. So wee need to change the zoom before start to run the scripts. Its better to have a code snippet in our framework to change this zoom setting right?
Here we go...

1. We can simply change the Registry values before Invoking IE
Function ChangeRegistry Dim objShell Set objShell = CreateObject("WScript.Shell")  objShell.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Zoom\ZoomFactor", "100000", "REG_DWORD" Set objShell = Nothing EndFunction This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try other options.

2. Use IE COM object and Change Settings
Function ChangeIEZoom Dim intZoomLevel, objIE  intZoo…

QTP - Common error messages

Always I am seeing  many of my friends asking for help if any error occurs while running script in QTP without googling for help. How much troubleshooting you guys are doing will directly reflect your knowledge on the tool. I agree, no one knows each and every error occurs in the software. But we can improve our knowledge by googling and doing workarounds...
Whenever the question "How much level you know QTP?" arrows me, always I am comfortable with the answer "below 10%". But after answered, my mind will have an inner thought like, What are the things I have to learn to fulfill the answer I have told because I never used lot of features in QTP.

Here I am listing out some of the errors, situations and what might be the original issue things etc. I hope this will give you some ideas to improve your debug ability and to solve your errors. Kindly correct me If I am wrong in any point.

Type mismatch:
- Mostly doing operations with different data types without doing type co…