Skip to main content

Sikuli - Handling Dialogs across Platforms

Hi all,


I am writing this post as I came to know this feature is some bit useful for Selenium Users who are running scripts across Windows, Linux and Mac platforms.


It is some difficult to handle dialogs while automating browser applications using selenium. Though its easy to automate those dialogs using native supported EXEs like AutoIt for Windows, dogTail for linux, ATOmac(http://pypi.python.org/pypi/atomac) and AppleScript for Mac, we need a common tool which can do the same operations in all platforms to ease the work.


So we are going to Sikuli
As its supporting all platforms, its not using any API to automate the dialogs and controls rather its using images of controls to do the operations.
It provides IDE to do the scripting on all OSs. Also no need for typing and own scriting. IDE itself provides the flow like


1. Find / Wait / Exists for some image
2. Do KeyBoard or Mouse Operations on that image


Finally you can export or save the script by .sikuli extension. This .sikuli folder contains the images and scripts for the specific test.


Now you can run the specific script from IDE. Also you can run the scripts from commadLine. This way you can call the sikuli scripts from Java Code as part of your selenium test.


java -jar sikuli-script.jar path-to-your-sikuli-script


For more information, visit their website http://www.sikuli.org
Also you can try SQUISH by FrogLogic


Also you can try below apps:
White - Windows Application Automation API (by Thoughtworks)
Frankenstein - Java Swing Application Automation (by Thoughtworks)
SWTBot - Java SWT based application automation (by Eclipse Group)

Comments

  1. great blog....please keep blogging more on Selenium

    ReplyDelete
  2. 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…