I think I stayed away too long and lost track of the discussion.... I can see that many agree that using Flex Cover is not the best option, right?
In which direction are we heading now? As I could catch up so far it seems that Adobe has a simple code coverage tool that we could work on, right? Do we have that code? Rafael Santos - SpectaTI @rafaelspecta On Wed, Mar 7, 2012 at 13:56, Alex Harui <aha...@adobe.com> wrote: > OTOH, I don't see why it couldn't be donated (or Apache couldn't just > re-write it based on the principle). I've never seen the code but it > sounds > simple. I suppose Adobe will continue to use the one we have for new AS > work related to gaming, but I don't think there is revenue tied to this > capability. > > I will add it to the list of things we will get around to donating. > > I haven't look at the link you sent, and I doubt it will meet your standard > of excellence, but it should be good enough for doing line checking. I > believe it uses flash.trace.Trace, so it will alias where you have one-line > conditionals, but you could probably handle that in the compiler. > > > On 3/7/12 7:44 AM, "Michael A. Labriola" <labri...@digitalprimates.net> > wrote: > > >> It might be better if we leverage the Adobe code coverage tool. > > > > Alex, > > > > What are the chances we can get code for this? I did some asking around > as > > well as looking through the forums. People who I believe know what they > are > > talking about claim that this tool fails to record coverage data in a > great > > number of circumstances. I am going to investigate further myself, but, > if > > this is going to be a closed tool, then it seems it will be eliminated > as a > > possibility very quickly. > > > > Mike > > > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > >
