I would guess that when compiling to JS FlexUnit won't work as FlexUnit requires the Unit Tests to run in a FlashPlayer instance ... Am I correct? So without a unit-testing framework to support JS Flex, I guess we couldn't actually do any Unit Tests with it.
Guess this problem is similar to the debugging problem as we currently wouldn't have any decent Debugging support to debug JS Flex applications from inside the IDE. Chris ________________________________________ Von: Alex Harui [aha...@adobe.com] Gesendet: Freitag, 12. April 2013 18:14 An: dev@flex.apache.org Betreff: Re: Meet 'marmotinni', an ASJS testing framework I haven't really looked yet, but why aren't we going to use FlexUnit? On 4/12/13 7:02 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > Hi, > > I've just committed a new testing framework to the ASJS repo. This > testing framework, which I've called 'marmotinni', following the > 'mustella' convention (Google it ;-), consists of FalconJX, asjs > projects, Java test classes (using the Selenium browser testing > classes) and an ant script to tie them all together. > > Right now there's only one test. It consists of a FlexJS project that > displays a single TextButton 100px from the left side of the browser > window. The ant script builds a JS release version using FalconJX. The > 'TextButton' Java class uses the Selenium framework to display the > FlexJS release build in a Firefox window, see if the button is there > and in the correct position. The result of the test is passed back to > ant and all artefacts are cleaned up. > > Please take a look and let me know what you think. > > EdB > > > > -- > Ix Multimedia Software > > Jan Luykenstraat 27 > 3521 VB Utrecht > > T. 06-51952295 > I. www.ixsoftware.nl -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
