> I see you made a couple commits as to testing in the project, how are we > doing this?
Adobe is willing to donate some test code but that might take some time due to legal review and other hassles. Adobe didn't develop many MXML tests so I was planning to starting writing an MXML test suite from scratch soon, and hope that others pitch in to help. As for ActionScript, starting with a port of Tamarin sounds like a good idea. (Adobe basically used Tamarin more-or-less as-is, but that probably creates legal issues for donation I also want to have tests of compiling the framework SWCs and any other "real world" code that people are willing to donate. > I noticed the code contains a lot of assert statements, what is the "rule" > for using these? The only rule I can think of is that asserts should not have side-effects. Developers just stuck in asserts when they wanted to do sanity checks that various conditions expected to be true are actually true. I think they have zero-cost runtime cost in Java when you don't enable asserts. > Do you have any plans for language level unit tests? Yes, I think we need unit tests for things like node classes in addition to tests of particular features, end-to-end, where you compile and run and check to see whether the program worked correctly. I was planning to start writing some unit tests for MXML node classes and hope that other folks will help me. I'll probably leave AS node classes to you and others; the eventual Adobe test donation might also have a fair amount of these. - Gordon -----Original Message----- From: Michael Schmalle [mailto:apa...@teotigraphix.com] Sent: Monday, September 17, 2012 5:25 AM To: flex-dev@incubator.apache.org Subject: Falcon :: Unit tests - as3 language level Hi, This is probably aimed at Gordon at the moment. I see you made a couple commits as to testing in the project, how are we doing this? I noticed the code contains a lot of assert statements, what is the "rule" for using these? Do you have any plans for language level unit tests? IE testing i++, a = 42, etc to node structures in the compiler.tree.* package. Do you eventually see having some type of sub structure set up so we can test all aspects of AS3 to make sure the compiler is parsing correctly (and MXML, CSS)? I have a bunch of unit tests covering packages, classes, interfaces all the way down to statements/expressions in the ASBlock library tests. I could use these as a huge running start for language coverage. I am willing to put a great amount of time into getting a base unit test system in place for low level parser nodes, not the IDefinition framework, the IASNode framework. So, I bet there is some way we can create a little test framework for language specific tests that I am talking about here. Thoughts? Having this test suite implemented will make it a lot easier to fix language bugs and introduce new features into the compiler's future. Mike -- Michael Schmalle - Teoti Graphix, LLC http://www.teotigraphix.com http://blog.teotigraphix.com
