Skip to main content

Automate testing of Flex / Adobe AIR application


Hi,
Automating special kind of UIs are always some complex and still more tools are keep on providing add-ons to support special UIs like Flex, SilverLight, etc. We have some good tools to automate flex 
applications easily. 
Lot of tools in market providing flex and silverlight support like market giants QTP, TestComplete, RFT etc.
Here are some other tools you can make,

Commercial Tools:
1. RIATest
Its a nice and simple tool which have good set of features and reporting. Its desktop application which can be used to automate adobe AIR, flex and windows based applications. 

2. RanoRex
RanoRex is a good tool but not got famous. Its Object identification is fully XPath like concept for both Web and Desktop apps called RanoreXPath. It have Object Spy, Object Repository, Recorder and PlayBack and good reporting like QTP.

OpenSource Tools:
1. FlexMonkey  
Its a open source adobe AIR application which provides record and playback support for flex, AIR applications. Simple tool which provides neat recording and playback. Can be used for unit testing of regression cases. Also provides reporting abilities.
Based on ActionScript and provides support many ways like
  • Desktop Adobe AIR application -- FlexMonkey
  • PlugIn for Selenium Tests - FlexMonkium
  • PlugIn for Android/iOS mobile testing - FoneMonkey
2. FunFX 
FunFx is also an open-source tool which provides record and playback of flex applications. It supports ruby language to code.

Comments

Popular posts from this blog

Some good Resources / Blogs / Sites for Selenium Users

Here I have listed out some good blogs and sites by extensive selenium automation users. Hope these will help you a lot. http://automationtricks.blogspot.com  - by NirajKumar http://www.theautomatedtester.co.uk/ http://testerinyou.blogspot.com   - by Naga/Mathu http://seleniumready.blogspot.com  - by Farheen Khan http://seleniumdeal.blogspot.com/  - Amit Vibhuti http://seleniumexamples.com/blog Sauce Labs and BrowserMob are companies doing cloud and extensive selenium automation services, products, etc http://saucelabs.com/blog http://blog.browsermob.com http://testingbot.com/ Cedric Beust -  creator of the TestNG Java testing framework. http://beust.com/weblog/ http://blog.reallysimplethoughts.com/  - by Samit Badle, Created many Selenium IDE Plug-Ins Available Colud Testing: 1. SauceLabs 2. Soasta 3. BrowserMob 4. CloudTesting.com  etc. Selenium Testing Products: 1. Twist by ThoughtWorks 2.  TestMaker by...

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 End   Function This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try othe...

Robotic Process Automation vs Traditional Test Automation vs Process/Task Automation

In IT industry, the term RPA is keep on hearing all sides of the walls for a while; and I was so confused about What's the difference from the test automation tools in the market and what's more into it. I did some search, understanding, and writing this post to share with you all. If I am not correct, PLEASE correct me. Traditional Test Automation: First, we have to recall the test automation tool QTP or UFT (Initially developed by Mercury Interactive Corporation(MIC) after WinRunner, then sold to HP, and again MicroFocus acquired from HP now). If you look into the architecture of this tool, MIC was trying to convert the testers into more efficient testers i.e. Testers were executing the test cases manually for regression suites, performance suites, etc. which had lot of repetitive tasks done by human testers instead of concentrating into new ideas or bug finding strategies to improve the quality of the product.  Thus WinRunner was introduced but it was demanding m...