I suggest that we first decide how we will test serialization,
otherwise we may make a low-level decision that will
make some high-level designs impossible
Thanks,
Mikhail
2006/4/28, Paulex Yang <[EMAIL PROTECTED]>:
> Stepan Mishura wrote:
> > On 4/28/06, Paulex Yang wrote:
> >
> >> Paulex Yang
On 4/28/06, Paulex Yang wrote:
>
> Paulex Yang wrote:
>
> > I think two serialization test is necessary in general:
> >
> > 1. test for Harmony itself, which ensure that the object can be
> > serialized/deserialized smoothly within Harmony VM/classlib
> > 2. test for compatibility with RI, which e
2006/4/28, Paulex Yang <[EMAIL PROTECTED]>:
> Anton Avtamonov wrote:
>
> > On 4/27/06, Mikhail Loenko <[EMAIL PROTECTED]> wrote:
> >
> >> As far as most of serialization tests extend SerializationTest then
> >> having serialization test cases included into a regular unit tests
> >> would cause that