flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Schmalle <apa...@teotigraphix.com>
Subject RE: [FALCON] Functional Testing
Date Wed, 14 Nov 2012 18:29:41 GMT
Ok so we have something basically setup like SWC tests.

I will be honest, I have NO IDEA how to do;

- run the SWF in Flash Player
- get the trace output, and check it

If you would set that stuff up sometime and give me a template, I'll  
get the idea.

Some of this stuff in the MXML AST is going to take a bit for me to  
digest. I spent 30 minutes stepping through code to see why AddChild  
can't have an id. I got to where AddChild as added as a child of the  
State and it did have an id set in the instance.

What I do not get is if there is a way I can back track to where the  
problem is added so I could start in the code closer to the problem.

I tried running the spark SWC tests and mx but there are some obvious  
errors that are going to take me a bit more time to digest where they  


Quoting Gordon Smith <gosmith@adobe.com>:

> The functional tests should simply call the entry point of MXMLC,  
> check that there are no problems, and run the SWF in Flash Player,  
> get the trace output, and check it. I also recommend that, as with  
> the parsing unit tests I've been writing, you don't have to  
> necessarily put the code to be compiled into a separated file. It  
> makes it easy to see what the test is testing when you can just look  
> at a String in the JUnit test.
> - Gordon
> -----Original Message-----
> From: Michael Schmalle [mailto:apache@teotigraphix.com]
> Sent: Wednesday, November 14, 2012 9:18 AM
> To: flex-dev@incubator.apache.org
> Subject: [FALCON] Functional Testing
> Hi,
> I finally have some time to get back into the deep recesses of the  
> compiler which I will say is probably the place I can afford to  
> spend my time.
> Now, We have unit tests and SWC functional tests. We do not have  
> MXMLC functional tests as it stands. Cyrill has a basic template he  
> has started in his GITHub account which basically mimics the way we  
> do it with a SWC.
> My question is, I can see this getting mammoth with mxml, fxg etc  
> sample files. How do we go about organizing this so we can test the  
> functionality that seems broken as we fix it?
> I have had thoughts of trying to reduce the Exceptions down to unit  
> testable artifacts but in the case of the FXGTranscoder exception,  
> this is impossible to unit test since it needs MXMLC to get to the  
> Exception.
> Any thoughts?
> Mike
> --
> Michael Schmalle - Teoti Graphix, LLC
> http://www.teotigraphix.com
> http://blog.teotigraphix.com

Michael Schmalle - Teoti Graphix, LLC

View raw message