As far as most of serialization tests extend SerializationTest then having serialization test cases included into a regular unit tests would cause that ALL the tests will extend SerializationTest that is not very good.
Thanks, Mikhail 2006/4/27, Stepan Mishura <[EMAIL PROTECTED]>: > Hi, > > I'd like to discuss naming conventions for serialization tests - does it > make sense to separate serialization tests from unit tests? > > For example, in module security tests for serialization were placed into > separate packages: > java.security.serialization > java.security.cert.serialization > java.security.spec.serialization > > Also it is possible to put tests in the same package but name them in > different ways, for example, > SomeClassTest.java – unit test for SomeClass > SerSomeClassTest.java – serialization test for SomeClass > > Or we won't separate serialization tests from unit tests and will test > serialization by adding corresponding methods to unit test, for example, > public void testSerialization1() > public void testSerialization2() > public void testSerialization3() > public void testSerializationCorrupted() > public void testSerializationIllegalValues() > > Thoughts? > > Thanks, > Stepan Mishura > Intel Middleware Products 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]
