Skip to main content

Selenium - Handling Windows


Testing web application is always fun and if you are automating your web application testing with Selenium, its even more fun. Unfortunately, like any other tool selenium has few limitations. One of the most annoying limitation of selenium is its inability to handle browser windows (Or any other expected or unexpected windows). When we automate any application which launches these windows (For example security warning windows, certifications windows and so on), we get stuck by the inability of selenium to handle them. I have seen people executing those automated tests but clicking on OK/Yes/Continue manually whenever these windows appear. This defies the whole purpose of automation, because tests can not be executed without human intervention.

Though it is not possible to solve this problem using Selenium (As far as I know), but we can certainly combine Selenium with other tools to solve it. One option is to use a small AutoIT script which will run in the background and wait for windows you are interested in. When that window / dialogue box appears AutoIT script will click on specific button or send required keystroke. If you are not familiar with AutoIT, here is the brief introduction from their site –

AutoIt v3 is a freeware BASIC-like scripting language designed for automating the Windows GUI and general scripting. It uses a combination of simulated keystrokes, mouse movement and window/control manipulation in order to automate tasks in a way not possible or reliable with other languages (e.g. VBScript and SendKeys).

You might have guessed that this is a windows only solution, but still its better than not having any solution at all :-).

Once you have installed AutoIT, actual script is very simple –

; Alters the method that is used to match window titles during search operations.
; = Match the title from the start (default)
; = Match any substring in the title
; = Exact title match
; = Advanced mode, see Window Titles & Text (Advanced)
;1 to -4 = force lower case match according to other type of match.
while(1)
Opt("WinTitleMatchMode","1")
;Pauses execution of the script until the requested window exists.
WinWait($CmdLine[1]);$CmdLine[1] is param 1 (after the script name)
$title = WinGetTitle($CmdLine[1]) ; retrives whole window title
WinActivate($title)
;Now click on Yes button to contibue running the script
ControlClick($title,"","&Yes")
;Send(“{ENTER}”)
WinClose($title)
Wend

When you launch this script from command line, it will continue to run in the background and whenever any window appears with the title you specified as parameter, it will perform the operation (Click on continue, yes, enter, esc etc as needed) you have specified.

Comments

  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

    ReplyDelete

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…