For the last few months, I’ve been hard at work on the latest version of FlexMonkey, and I am excited to announce that it is being released as a beta today. For those that do not know, FlexMonkey is the open source functional testing tool for Flex and AIR. Along with this announcement, James Ward and I published an introductory article at Artima.com that will give you a full overview of the tool.
We are calling this version “FlexMonkey Reloaded,” as I’ve reworked all the major parts of the tool. Here is the high level overview of the updates:
- Brand new console: New Flex 4 console with drag and drop paradigm to make test creating quick and easy.
- New Test Elements: A number of new test elements have been added (Set Property, Call Function, Store Value).
- Continuous Integration/FlexUnit: FlexMonkey now generates FlexUnit 4 tests, and thus allows for taking advantage of FlexUnit’s CI infrastructure (Thanks to Mike Labriola for help getting this integrated).
- Internals:
- Countless Code Refactors
- Removed Mate Removed the Mate framework in favor of a simple custom EventBus.
- MonkeyLink Communication Clean-up Cleaned-up to make connection between application under test and FlexMonkey more robust.
- FlexUnit Core Runner: In addition to generating FlexUnit source, the console now uses FlexUnit for its internal runner infrastructure.
You can get the FlexMonkey Reloaded beta by downloading it here.









Pingback: Tweets that mention FlexMonkey ‘Reloaded’ Beta Release | Jon Rose's Blog -- Topsy.com
Awesome !! Integration with FlexUnit 4 is a BIG +
Pingback: Flex Testing with FlexMonkey Reloaded: Introduction Video (Part 1) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Getting Setup (Part 2) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Verify Component Command (Part 3) | Jon Rose's Blog
Pingback: Testing Flex Apps with FlexMonkey Reloaded
Pingback: Flex Testing with FlexMonkey Reloaded: Verify Expression Command (Part 4) | Jon Rose's Blog
Hello,
Can I test my application on the fly using Flex Monkey? I mean without adding any libraries / modifying the the source code?
You do have to add in the library, but do not necessarily have to modify code.
-Jon
Pingback: Testing Flex Apps with FlexMonkey Reloaded (Adobe Flash Platform Blog)
It still means re-compiling the source code. Can we have some kind of mechanism where in we can test the application deployed on production server? Using LocalConnection or similar technique?
The Automation and FlexMonkey libraries need to be linked into the code for everything to work. In the past, we’ve had some attempted features that tried to do what you are asking by linking everything together at runtime by swfloading the testing application, but because of limitations in the Flash platform they rarely worked, so we’ve no longer supported any other way of running. In terms of functional testing theory, it would be unusual to use FlexMonkey with a production application.
-Jon
Pingback: Cool Stuff with the Flash Platform – Molehill 3D Special Edition – 3/4/11 | Finding Out About
Pingback: Flex Testing with FlexMonkey Reloaded: Verify Grid Command (Part 5) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Store Value Command (Part 6) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Set Property Command (Part 7) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Call Function Command (Part 8) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Retry (Part 9) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Continuous Integration (Part 10) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: FileBrowse Dialog (Part 11) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Parameterizing Generated Code (Part 12) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Debugging Problems (Part 13) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Auto Run Demo Application (Part 14) | Jon Rose's Blog
Pingback: Flex Testing with FlexMonkey Reloaded: Programmatic Test Generation (Part 15) | Jon Rose's Blog
hi Jon,
Thanks for the nice article.
In one of the comment you have mentioned “…because of limitations in the Flash platform they rarely worked…”. Could you please elaborate on this? I mean what kind of limitations etc?
Thanks
–
Mahesh
Hi Mahesh,
I don’t remember the context of this. What was I referring to?
Thanks,
-Jon
Hello,
I’m testing with excellent results the FlexMonkey Reloaded. I am with the following difficulty when trying to use the automatically generated class to simulate the operation: I did a simple test to fill login and password at the login screen of the system. This test works fine when I’m in flexmokey environment. When I try to use the class FlexMonkeyTestController inside my application, the values that are inserted in the text boxes are duplicates (eg “loginlogin”). Can you help me?
Hi Jon,
Please see the attachment for FlexMonkium recorded code
try {
if (proc.getBoolean(“isFlexMonkey”, new String[] {” “})) break;
} catch (Exception e) { }
Thread.sleep(500);
The Entry Point is the column name being clicked but its recorded as value=\”vteamId\”/>.
The Main problem i am facing is that recorded snipped of code is not playing back but whatever the click the tool is clicking is the column name dybnmically added to advanceddatagrid.
Thanks in Advance,
Nagesh