incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas Kwiatkowski <>
Subject Re: Starting with the Whiteboard Code
Date Sun, 05 Feb 2012 17:05:47 GMT

There are no unit tests for each module.  They do not exist.  Adobe has
typically only done functional testing (using their custom testing suite).
 One of the early goals of at least some of the PPMC members is to make the
SDK unit-testable.


On Sun, Feb 5, 2012 at 10:02 AM, Martin Heidegger <>wrote:

> Hello Alex,
> Thank you for the clarification. I sure sounds like a lot of good reasons
> as to why this might take a while.
> Your efforts are awesome!
> However: I have another thought popping up: Do you think once you arrived
> at the unit tests it would take a lot of effort to publish the unit tests
> by the module? Listening to your elaboration the whole effort could mean
> more than a month of work from your side. The parts of the framework to
> which unit tests are available could be worked on before everything is
> done. Well, that's just a thought I don't mean to be pushy.
> yours
> Martin
> Side note to myself: Avoid copyrighted material for test cases. ;)
> On 05/02/2012 22:03, Alex Harui wrote:
>> Every file Adobe donates has to be scrubbed.  Carol and I are fully booked
>> getting SVN history and JIRA.  Next is the compiler for which we keep
>> hitting legal issues.  After that is the test suite which we know needs
>> every font file replaced or re-scripted, and tons of images reviewed
>> manually for copyright infringement.  For example, an image item renderer
>> test used Adobe product logos and each of those logos needs to be replaced
>> and the baseline comparision images re-made.  It is just going to take a
>> while.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message