>FlexJS will keep metadata on the JS side, probably as simple properties on the >classes and/or functions. I imagine we'll write a library that abstracts the >fetching of metadata and returns it as an array of strings or maybe as JSON. >If we could easily retrofit the metadata fetching in FlexUnit, would going >this route become more interesting?
It could be only as it will keep the parallelism. I am of two minds about it. Ultimately in some of our previous cross-compilation work we decided to cross-compile on top of a native javascript library >OK, thanks. Any idea why the JS community did not leverage Junit? Did they >all just fall in love with newer approaches like behaviors? Yes to behaviors but also because they are not cross-compiling so they don't have Annotations and the like which JUnit relies upon. Also, honestly, when writing JS by hand you wouldn't write it in the same ways that a Flex or Java app is written. It tends to be more functional and less OO. Further, the need for mocking and other unit testing ideas in Java are less needed in a JS environment without access restrictions and with first class functions. Mike
