Having good results with FlexUnit here, using Parsley IoC instead of Cairngorm or what-have-you because of the advantages to mocking/testing with IoC/Dependency Injection (when will the community settle on a name for that pattern so I can stop using both! :)
We have a structure like: /trunk/common /trunk/web /trunk/test For shared, web-client and test code respectively. Web and test both pull in the common SWC. Still very skeletal at this point so there could be hurdles further down the road we're not aware of yet, but all going smoothly for now. I can even step through my unit tests in Flex Builder -- something I wasn't sure I'd be able to do as there's no FlexUnit plugin for Eclipse that I could find... Oh, last thing is we are using Antennae common tasks and targets for our Ant builds, just because it's the first thing we stumbled across and seems to have fairly good structure for multi-project solutions. On Tue, Dec 16, 2008 at 05:49, Errol Thompson <[email protected]> wrote: > I am fairly new to Flex but have a reasonable amount of experience with > test-driven development in Java and .NET. > > I have been told that test-driving Flex development is not possible. I am > not convinced as I have been told similar things on other projects in the > past and then proven that they are possible. > > I am wondering: > > 1) How many people actually use a testing framework (FlexUnit, Fluint, > FUnit, AsUnit) when doing Flex development? > > 2) Does using a testing framework change the way that you structure your > Flex applications? > > 3) How many use test-driven development with the Cairngorm framework? > > --------------------------------- > 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.thompsonz.net > --------------------------------- > > -- Cheers, Jules -- Jules Suggate Owner and Technical Lead Uphill Sprint Limited +64-21-157-8562
