For what it's worth, it's true that FlexMonkey is not a unit testing framework (it's more about generating functional tests for the UI), but it's fantastic (especially 0.6+). I first found out about it from this list earlier this week, and about a day later, I started moving our tests to it (from FunFX).
Initially getting it working in Flex 3.0 was a pain (it is built against a library that was built against 3.1, which introduced some breaking api changes), but now that it's running, it's a great tool. It records interactions and essentially generates FlexUnit tests for you (in theory, it can generate test for any unit testing framework with asynchronous test case support, but it's currently tied into FlexUnit). I highly recommend it. -- Maciek Sakrejda Truviso, Inc. http://www.truviso.com -----Original Message----- From: Errol Thompson <kiw...@acm.org> Reply-To: flexcoders@yahoogroups.com To: flexcoders@yahoogroups.com Subject: RE: [flexcoders] Which Unit Testing Framework to use? Date: Sat, 10 Jan 2009 13:00:02 +1300 > After a brief search on flex unit testing I found that > FlexUnit is supposed to be the leader of the pack. I am interested in why you think FlexUnit is the leader of the pack. I know that Adobe have adopted it but its syntax for asserts and assert options are limited. On my blog (http://kiwi-et.blogspot.com/2008/12/assertive-tests.html), I compared the asserts available for FlexUnit, Fluint, FUnit, and FluxUint. I have written other blogs which talk about the differences between the frameworks. I haven't explored the use of FlexMonkey as the description of what it did didn't match my requirements. On my current project, we are using FlexUnit. --------------------------------- Errol Thompson Kiwi-ET Computing Education Research Wellington, New Zealand Phone: +64 21 210 1662 E-Mail: kiwiet (at) acm.org kiwiet (at) computer.org Web: www.teach.thompsonz.net ---------------------------------
