Flex Automation Testing

Intro

I had the chance to straggle with Flex automation testing and Mercury QTP tool here it comes...

Flex automation testing is an OOTB feature, you can easily test your application all you have to do is to follow a simple installation process and you are good to go.
http://labs.adobe.com/wiki/index.php/Flex_3:Release_Notes#Installing_and_Configuring_Flex_Automated_Testing
See also attached PDFs for further knowledge about flex automation and QTP.

First tip: follow the installation instructions carefully and don't miss any step.

Automation tool
I had to test my Flex application (customer is always right :) the first thing I did was to look for a working example, I found this example: http://www.adobe.com/devnet/flex/samples/flex_store_v2/
Ok so I can see a Flex application (:o) but what can I do with it?
In order to actually Record and Play Flex application actions we have to use an automation tool. There are commercial tools like Mercury QTP (you can find maybe one or two in additional but not at the same level) or you can write a custom agent (http://www.adobe.com/devnet/flex/samples/custom_automated/) which can be splendid but taking it to high level is not a trivial task.

But what do you do if you need an open source tool?
After a little research I found the closet answer to QTP, meet FunFx (http://funfx.rubyforge.org/)
FunFX A Ruby tool for functional testing of Adobe Flex applications

FunFX is the only free alternative to achieve functional testing of Adobe Flex applications.

See the user guide movie, awesome start (http://funfx.rubyforge.org/user-guide.html)

I have played with it a bit, it's nothing like QTP which is much powerful but it's a good tool for basic testing and it probably will get better since it's still on a minor version.

 

Component API

After playing around with QTP and FunFX automation tools I went back and started to make my flex application testable. As I already figured out flex components already have its automation implemented (see IAutomationManager), it means that if you have compiled your application with the automation testing libraries all you have to do is using the tool and it'll record and play your actions.

To be continued....
Next some unpleasant surprises.
 

 

Thank you for your interest!

We will contact you as soon as possible.

Send us a message

Oops, something went wrong
Please try again or contact us by email at info@tikalk.com