Archive for August, 2008

FlexUnit on Adobe Open Source

flexunit.jpg
Following on from the news that Cairngorm has been moved to Adobe Open Source, it is my pleasure to announce that FlexUnit, the unit testing framework for Flex applications, now has a new home on Adobe Open Source.
FlexUnit started its life almost 5 years ago, when I first wrote AS2Unit; at that time, it home was the iteration::two website. FlexUnit was borne from that project, and was released shortly after Flex 1.0 in March 2004.
With the release of Flex 2, a team from Adobe Developer Relations migrated the framework to ActionScript 3 and gave it a new home on Adobe Labs. However, it was soon on its move again, and ended up on Google Code as a 0.85 release of as3flexunit.
Since that time, a number of bugs have been identified, and a number fixed, but there has been no real visibility of ownership; no-one has the responsibility to build and test and release new versions to the community and the 0.85 version is fast approaching 2 years old.
We see this move as bringing FlexUnit back to its Adobe home, where it can get the attention and care it deserves.
Adobe Open Source brings a number of benefits:
* Source available via a Source Control System (Subversion)
* Availability of a bugbase for bugs and enhancement requests (JIRA)
* Developer forums for the discussion of features and roadmap
* Ability to submit code patches
Alongside this move, we’ve also taken the opportunity to do some bug fixes and have also add some new features to FlexUnit. The codebase for this release is based on revision 20 from Google Code. We realize that there have been a few subsequent changes made to that codebase since we had to branch to make our own bug fixes and enhancements, and we look to the community to reintegrate any of these changes, as necessary. We have chosen to go down this route rather than delay the release further.
The most visible set of changes to FlexUnit, and something you’ve probably already noticed from the screenshot above, is in the graphical test runner, designed by the User Experience team at Adobe Consulting.
Within the runner, we’ve added more information about the tests being run. We’ve provided the average number of asserts per test case, and also the number of asserts in each individual test case.
flexunit-summary.jpg
When tests do fail, we’ve extracted the failure information to make it clearer to the user, and, so long as you have compiled your tests with debug set to true, and are running with the debug flash player, you will also see the stack trace, to give that extra level of information not necessarily previously available.
flexunit-results.jpg
Finally, you can now also filter your test results, for those larger projects where you have hundreds of test cases.
You can filter on individual test case names, test names, expected results or actual results, and also choose to see results based on all test cases, only those with errors or failures, or just empty test cases.
flexunit-filter.jpg
We are incredibly excited about this move, and look forward to the community getting involved through the submission of enhancement requests, code patches, documentation and taking part in the discussions around FlexUnit.
I was hoping to contact the project members of the existing as3flexunit project; unfortunately, Google Code does not let me easily identify the current members. So, if you wish to contribute to the project, please contact me.
The FlexUnit home page on Adobe Open Source can be found here.

Cairngorm on Adobe Open Source – One Week On

So, Cairngorm has been on Adobe Open Source for over one week now, and I thought I’d summarize what’s happened since.
It has been interesting to watch the community response to my announcement. To Adobe Consulting, this was a move of an already open source project from Adobe Labs to Adobe Open Source, but while the response has been extremely positive, many of the reports read as if Cairngorm becoming open source was something new.
I guess this says something about our previous messaging, and the fact that the setup on Adobe Labs wasn’t the same as Adobe Open Source, where we now a full governance and have the source code hosted on Subversion and available to all, rather than a single ZIP download of the source.
As i explained in my announcement, we made a conscious decision not to add any new features in the process of the move. We did, however, provide the facility for community feedback, and already, we’ve had a good amount of involvement.
Over on the Cairngorm Forums, we’ve had various discussions, including those on creating a test suite for Cairngorm, tooling support for Cairngorm within Flex Builder and how we should approach extending Cairngorm.
The Cairngorm Bugbase has sprung into life too, and Christophe Herreman has already submitted patches containing some initial unit tests, alongside two other bug reports with patches. We’ve also had an enhancement request, for better support for Cairngorm with Flex Modules.
JIRA, on which the Cairngorm bugbase runs, has a voting facility, so please get invovled, and vote on the bugs and enhancement requests you think should be part of a future release.
What next?
A team from Adobe Consulting met on Monday of this week to discuss the Cairngorm roadmap, both in the short-term, to apply the patches provided and ensure Cairngorm is fully up to date with the latest releases of the Flex SDK, BlazeDS and LiveCycle Data Services, and also looking to the future, and Cairngorm 3.
We’ll be socializing our thinking over the coming weeks
In the meantime, we encourage you to get involved in the discussions taking place on the forums or to submit enhancement requests to the bugbase.

Cairngorm Moved to Adobe Open Source

Adobe Consulting is pleased to announce that the Cairngorm Micro-architecture has moved onto Adobe Open Source.
Its hard to believe that Cairngorm is approaching 4 years old – Steven and I announced it at the Max conference in New Orleans in October 2004 and the first version was released soon thereafter.
We’ve gone through a number of different versions since then, but each one has always held true our vision: Provide a lightweight MVC architectural framework around which to build Rich Internet Applications with Adobe Flex or Adobe AIR.
The latest version, Cairngorm 2.2.1, was released back in October 2007 and, although we at Adobe Consulting consider that being a good reflection as to the maturity of the framework, there have been some questions on when the next release would be made available and what new features it would have, alongside some specific feature requests.
At Adobe Consulting, we’ve always had a minimalist approach to Cairngorm; we don’t want to add feature for feature sake, add functionality that doesn’t belong within an architectural framework, or introduce another design pattern into the mix because it’s the latest fad in the software industry. The framework is there to allow us to build well-architected software solutions, and we’ve only ever added features we truly believe helps us do that.
There are no new features in this release – at this time we are simply moving Cairngorm 2.2.1 from Adobe Labs to Adobe Open Source.
However, we do listen to the community and to our customers, and this announcement is in response to this invaluable feedback. We hope that this launch will emphasize the commitment that Adobe has to the framework, and reinforce the message that the framework is the one that Adobe Consulting visibly advocates.
There are many benefits to having Cairngorm on Adobe Open Source. Alongside having a well defined home for downloading the framework, its documentation and samples, Adobe Open Source also provides additional resources one would expect of an open source project:
* Source available via a Source Control System (Subversion)
* Availability of a bugbase for bugs and enhancement requests (JIRA)
* Developer forums for the discussion of features and roadmap
* Ability to submit code patches
Alongside this move, we are also introducing a level of governance, a charter that explains how the Cairngorm project will be managed, and how leaders in the Flex community can get involved in the project.
We are also extending an open invitation to the community to submit bugs or feature requests and take part in the Cairngorm discussion forums.
The community has read-only access to the Cairngorm source code by default, and contributors will also be able to submit code patches.
We are incredibly excited about this move, and look forward to the community getting involved in the framework, through the submission of enhancement requests, sample applications, code patches, documentation and taking part in the discussions on the future direction of Cairngorm.
The Cairngorm home page on Adobe Open Source can be found here.