On Thu, Feb 9, 2012 at 10:09 AM, Jonathan Campos <jonbcam...@gmail.com>wrote:
> Just dropping in 2 cents. > > While I too use FlexUnit and think that a consensus would be good on how to > write tests, my fear is that we shouldn't say "use this one". > > There are other contributors to Flex, such as ASUnit, that we would be > snubbing. > > Sadly I feel the best solution is just let people write the tests and > whatever they choose to use that is up to them. If a group of individuals > want to all write using one version that is up to them, but I don't know > about saying that one is the supported or only choice. > > -- > Jonathan Campos > Several issues here, I think we should all stick to the same unit testing frameworks for consistency so we can easily merge each others works. But ASUnit in particular I think is something we should not be considering. Take a look at their page: http://asunit.org/ Not a single resource at the bottom that are supposed to be their resources for getting started work anymore. And if I remember correctly, this project has been abandoned for at least a year or two because the author is like either a JS or Ruby guy. This is bad if we suggest people should, or could, use ASUnit. At the least, we should say don't use ASUnit because of X reason, and I think those reasons right now are a.) its abandoned, b.) docs suck, c.) FlexUnit has built in support in both IntelliJ and Flash Builder. -omar
