Hi,
As Justin said, most of the tests are done comparing bitmaps, that's more
functional testing than unit testing but there are also method, property and
error tests.
It's difficult to say the percentage of code coverage we've got, adobe has a
tool doing that but I don't know the status of its donation but knows that
it's not 14000+ tests we've got, it's 36000+ tests, theoricaly, they all
should pass on mac and windows with Flash Player 10.2 to 11.6+ but it hasn't
been fully tested on each ones as stated before, what I can say is that I
ran the test suite few days ago and on my windows 7, I had only 1 test
failed and it seems to pass on mac, for the 4.9.0 I tested it against FP
11.5 and had 4 tests failed which means praticly, we're > 99.988 % of passed
tests on players from FP11.1 to 11.5 and those failed tests are only few
pixels rendering differences, nothing catastrophic and as you can see,
unlike Adobe SDKs, we support more Flash Players, it means that you can
leverage users with low requirements regarding the FP version they use or
leverage the newest flash player features.
-Fred
-----Message d'origine-----
From: Justin Mclean
Sent: Tuesday, February 19, 2013 7:47 AM
To: [email protected]
Subject: Re: Worker/Mutex/Condition
Hi,
Third, do you guys recommend we go with 4.7 for a production update, or do
you feel confident in the latest releases? Is there a quantitative measure
of confidence, ie code coverage, 97% passing, etc.
Forgot to say policy is all test must pass for it to be an official release.
Justin
