AsUnit 3.x Supports Asynchronous Test Methods and Flex!

Ali Mills — Thu, 21 Sep 2006 02:15:33 -0000

That's right, there is a new build (only available in Subversion) that finally supports asynchronous test methods, and the Flex framework.

From any TestCase, you can now call addChild(child) with a Visual Entity that extends UIComponent, or one that does not. The child will be added to an appropriate parent depending on whether or not it's a UIComponent.

We also support asynchronous test methods! The base TestCase has a new method called addAsync. Just hand it your event handler, and send the function it returns to your event subscription, and AsUnit will do the rest!

Check out the sources in subversion for more info.

Version 2.6 Release Candidate posted, with MTASC Support!

Ali Mills — Tue, 24 May 2005 19:20:06 -0000

The version 2.6 release candidate has finally been posted!

Many thanks to those of you in the community that helped to make this release possible. These include Ralf Bokelberg, Erixtekila, Keith Peters and Daniel Wabyick.

This release includes the following:
------------------------------------------------
Version 2.6 May 24, 2005
------------------------------------------------
- Implemented full MTASC support thanks to:
Ralf Bokelberg, Erixtekila, and Daniel Wabyick
- Added com.asunit.util.TextFile object for simpler
loading of external files during unit testing.
- Added Eclipse directory names to the ignore list for the
Build Test Suites command so that it will no longer include
those directories in the TestSuite.
- Fixed assertEquals method in TestCase according to Keith Peters' comments
- Fixed problem with setCurrentMethod according to Caleb's post so that
assertion failures will be accurate even when using
asynchronous test cases.

Version 2.5 Released with FLEX Support!

Ali Mills — Sun, 09 Jan 2005 02:35:13 -0000

AsUnit version 2.5 was released today with support for Macromedia Flex version 1.5. While there is not yet a simple installation routine for Flex, the application framework does in fact compile and present useful debug output. Another helpful feature for Flex developers is the much-needed Sys.println functionality that will output text messages directly in the AsUnit User Interface.

Here are the release notes:
------------------------------------------------
Version 2.5 January 8, 2005
------------------------------------------------
- Implemented AsUnit for Flex. After manual user installation, the .as
files will now compile and communicate correctly.
- Added underscore prefix so that Sys.println and Unit Tests are now
cross-domain compatible.
- Updated TestCase.attachMovie to support optional arguments.
- Added the TestCaseXml object and integrated into the TestCase.
- Fixed asynch test bug where failures were reporting invalid classname
as source class.
- Fixed LocalConnections in UI so that they close onUnload
- Added optional Sys.println output to AsUnit UI which also supports
cross-session memory of user selection.
- Removed extraneous output from Failed Assertions.
- Fixed "Add to Library" so that it will also make the new Class extend
MovieClip.

Version 2.0 Released!

Ali Mills — Sun, 24 Oct 2004 02:37:07 -0000

We have released version 2.0 of the AsUnit Test Framework!

This release owes huge thanks to the work of Tibor Claassen as he thought of and implemented many of the features described below.

This release includes:

- Fixed Auto-Open for Mac Users
- Optionally Auto-Update TestSuites whenever a new Class is Created.
- Added Link to failed tests, so that you can click directly from the Unit Test Output Panel and open the file.
- Added new "Local" Output Panel, so that Sys.println traces can be viewed directly in the .SWF file without the IDE open.
- Simplified Test Templates, so that users can manipulate what gets created when they call "Create Class"

Finally - Full Mac Support! Version 1.09 released!

Ali Mills — Tue, 31 Aug 2004 08:09:46 -0000

- Added new custom property named FLfile.separator which will be either "\\" or ":" depending the user's platform.
- Added new jsfl file to manage the separator assignment.
- Updated Create Class to work on macintosh
- Updated Build Test Suites script to work on macintosh
- Tried to debug the Local Output Panel but had no success. It won't display correctly from anywhere other than the asunit build directory. Perhaps still missing a file?

Released version 1.08!

Ali Mills — Sun, 29 Aug 2004 03:11:13 -0000

- Added "Build Test Suites" command. This command will search through the current working directory of the active .FLA file and for each directory found, will create an AllTests.as file. The AllTests.as files should automatically include each other and any *Test.as files found there is no longer a requirement that users manage inclusion of test cases in order to build test suites. This command should automate the process.
- Added runtime version checking. The AsUnit UI file will now check an xml document that is stored remotely to find out if you have the latest version of the framework. If a user does not have the latest version, they will receive a nag in the output panel.
- Added "Local Output Panel" to the framework so that users will soon be able to instantiate a text output panel directly within their currently running swf and thus be able to receive test output outside of the Flash IDE. This functionality is being branched directly from the Sys.println command and is not yet fully integrated.
- Fixed error in the Assert Class: Would alway throw error if user compiled to Flash 6 player.
- Fixed error in the Assert Class: Would throw JSFL error because of invalid chars in the output.

The new Local Output Panel can be implemented from any timeline as follows:

import com.asunit.controls.*;
// getInstance requires:
// @param ref:MovieClip
// @param num:Number (a valid depth)
var lop:LocalOutputPanel = LocalOutputPanel.getInstance(this, 1);

Updated the Example Files

Ali Mills — Thu, 26 Aug 2004 23:32:52 -0000

I just posted an update to the Example files.

The example files no longer use a duplicate package structure, but instead put the TestCases in the same package as the classes under test.
We now also use Test as a suffix rather than a prefix for TestCases and this change is reflected in the example app.

Updated project to release version 01.07

Ali Mills — Tue, 24 Aug 2004 22:55:03 -0000

Implemented a number of bug fixes and feature enhancements to the "Create Class" Command.

Following are the Release Notes:
- Updated Create Class Command so that it no longer creates a parrallel "test" package, but creates the new Test Class in the same package as the original class.
- Updated Create Class Command so that it suffixes the word "Test" to the class name rather than prefixing it.
- Updated the newly created class template so that it uses "linkageId", "classRef" and "serializable".
- Updated the newly created test class so that it uses "linkageId" rather than "className".
- Updated the Create Class XUL file so that it asks whether the new class is a MovieClip without a related Symbol. (Will prepend "__Packages" to the "linkageId").
- Updated Output Window output for successful class text so that double backslashed were turned into single forward slashes.
- Added "extends MovieClip " to the class declaration if "__Packages." prefix is selected.

Released Full Version

Ali Mills — Wed, 11 Aug 2004 20:33:26 -0000

On August 11, 2004 we have finally released a full version 1.05 product.

This release includes some minor bug fixes to the Sys.println functionality and enabling the Create Class command for windows users.

We expect to release another minor revision with more robust mac support shortly.

Flash ActionScript 2.0 Unit Test Framework Beta Released

Ali Mills — Sat, 08 May 2004 05:58:23 -0000

Ali Mills and Luke Bayes are excited to announce a new Open Source ActionScript 2.0 Unit Test Framework named "AsUnit". This library is being released on SourceForge.net as beta software (under the LGPL license), and has been successfully used (in various forms) within a range of projects over the past 5 months. We have been involved in test-driven development for a short time now and are very eager to share the results of our efforts with others. Our goals with this release include wide-spread adoption, collaboration and knowledge sharing.

As some of you may know, there are already two (that were aware of) other Unit Test Frameworks available for Flash. These are, "ASUnit" from Robin Debreuil, and "As2Unit" from iteration::two. Each of these initiatives and certainly these two groups, carry our complete and undying respect and gratitude as they have laid a critical foundation for this work to be done. Unfortunately, neither of these releases really succeeded in meeting our (possibly unique) day to day testing needs. Some of these needs are as follows:

- Tests should be written in pure ActionScript 2.0 and require absolute minimal interaction with the Flash MX 2004 IDE. (We use Sapien PrimalScript for all of our AS 2.0 Development and encourage anyone else to do the same.)

- Source Code should be freely available so that we (or others) can quickly fix whats broken or make changes to suit specific and possibly unique needs.

- Should provide GUI output that is as similar as possible to existing Unit Test standards from other languages. (JUnit)

- Should provide minimal notification for successful system tests so that failures receive the attention that they deserve.

- Should not write directly to the native Output Window so that our (very useful and occasionally desirable) compile errors do not get lost.

- Should allow tests to be executed (and displayed) from both the IDE Test-Movie Player, and the Browser.

- Should provide current and extensive documentation combined with sample files. (Admittedly, this is a weakness in our current build, but perhaps *you* can help with this issue and receive massive honors and notoriety!)

- Would like some facility for quickly creating Classes from Templates *along with* their associated Unit Test Class. (*A feature of our release that has already saved us countless hours of menial and redundant typing.)

While this release really succeeds in meeting our particular development needs, it may not be exactly what you want. This is why weve released it under the LGPL license. You can contribute to help make it what you want or you can try out one of the other Flash Unit Test options that are available.

Please check out the following links to learn more about this exciting release and/or Test-Driven Development in general:

To download and start using the "AsUnit" framework:
http://sourceforge.net/projects/asunit/

To start helping with development and maintenance of the framework:
http://sourceforge.net/project/memberlist.php?group_id=108947

Post notes, ideas, thoughts, and errata to our Project Forums at:
https://sourceforge.net/forum/forum.php?forum_id=374043

Interested in reading the ideas bouncing around during initial development:
http://lukebayes.blogspot.com/

Robins Release of "ASUnit" (His blog is a must-read)
http://www.debreuil.com/FrameworkDocs/UnitTestingOverview.htm

iteration::two:
http://www.iterationtwo.com

iteration::two (AS2Unit):
http://www.as2unit.org

Test Driven Development / Extreme Programming:
http://www.junit.org
http://www.extremeprogramming.org
http://www.xprogramming.com

Thanks for reading and we hope to hear from you soon!

Ali Mills | Luke Bayes

Recent posts to news