harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Zakharov" <alexei.zakha...@gmail.com>
Subject [classlib] [testing] java.beans tests
Date Wed, 14 Jun 2006 12:26:42 GMT
Hello to everyone,

I am currently investigating tests for java.beans module. As far as I
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.
For point 2, I believe we should rewrite or delete such tests.

Thoughts, suggestions?

Alexei Zakharov,
Intel Middleware Product Division

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message