>Correct, but as I understand them, Mustella tests are pretty specific to
>components (e.g., display objects). Does the rest of the framework have some
>sort of test coverage, or am I misunderstanding Mustella?
You can think of mustella tests as executing a series of actions or steps
against an object and having the ability to wait for event to do property or
even image comparison. So far as I know, the only 'test coverage' numbers that
Adobe used to define their test coverage came from running the mustella
suite... so any other APIs were exercised by the use of mustella component
interactions. Further, and maybe Alex can comment on this as I do not know for
sure, I believe the test coverage information quoted by Deepa and others used
the coverage plugin on labs they built for Flash Builder. This used the
profiler API and was effectively fairly useless method coverage.
For example:
function doThing( val:* ):void {
if (!val) {
return;
}
//5000 more lines in this method
}
Therefore if this method was called with a null, the whole method and all the
code that did not belong in it was considered 'covered'
Mike
