On 4/28/06, Anton Avtamonov wrote:
>
> On 4/28/06, Stepan Mishura wrote:
> > On 4/27/06, Anton Avtamonov wrote:
> <SNIP>
>
> Which approach is better is very personal :-). I would ay that the
> second one. It is more intention-revealing. Really, when you override
> testDeserialized() you don't see how and where it is used. With
> properly used delegation pattern the tests would be:
Anton, when you override setUp() and tearDown() methods you also don't see
how and where they are used. Do you use them or copy/paste setUp/tearDown
code to every testing method?
Thanks,
Stepan.
testSelfSerialization() {
> Object deserialized = SerializationTest.serializeDeserialize(original);
> assertEquals(original, deserialized);
> }
>
> In case deserialization assertion for the particular object is not
> just assertEquals() it will be well-shown.
>
> Similarly to test against stored serialization form (golden file).
>
> Wishes,
> --
> Anton Avtamonov,
> 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]
>
>
--
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]
