Hi Alexei
2006/6/14, Alexei Zakharov <[EMAIL PROTECTED]>:
Hello to everyone,
I am currently investigating tests for java.beans module. As far as I
Cool!
understand there were two separate contributions of java.beans tests
from two different parties. And these contributions were merged into
the single combined test suite we have now in svn. As a result
currently we have about 400 test case failures (excluded) out of
approximately 1200. After spending some time on this I realize that we
have two types of issues here:
1. Test checks the compliance with very deep detail of RI's behavior (that
is not in spec).
2. Test expects the behavior that differs from the RI's behavior as well as
from our implementation's behavior.
As for point 1, I'm unsure here. Do we really need to be completely
identical to the RI in terms of public methods behavior? Some RI
decisions are strange.
Please publish all those differences, we will need to make decisions on
case-by-case basis.
For point 2, I believe we should rewrite or delete such tests.
If once you rewrite a test you get a duplicate of another test then
the test might be
deleted. Otherwise it should be fixed.
Thanks,
Mikhail
Thoughts, suggestions?
--
Alexei Zakharov,
Intel Middleware Product Division
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
