Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: local policy)
Message-ID: <20121114121751.1803697m4p5r4enz@www.teotigraphix.com>
Date: Wed, 14 Nov 2012 12:17:51 -0500
From: Michael Schmalle <apache@teotigraphix.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Subject: [FALCON] Functional Testing
MIME-Version: 1.0
Content-Type: text/plain;
 charset=ISO-8859-1;
 DelSp="Yes";
 format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.3.11)

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