[infinispan-issues] [JBoss JIRA] Updated: (ISPN-59) Add unit test that verifies number of written bytes

[Galder Zamarreño (JIRA)]

     [ https://jira.jboss.org/jira/browse/ISPN-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Galder Zamarreño updated ISPN-59:
---------------------------------

    Attachment: org.infinispan.marshall.MarshallersTest-v2-onlyobjecttable.xml


Attaching v2 after implementing ObjectTable based solution. This drastically reduces the sizes of payload. Examples:

testListMarshalling
  472(v1) -> 393(v2) (vs 334 with MarshallerImpl)

testImmutableResponseMarshalling - passed :)

testSingletonListMarshalling 
  100(v1) -> 77(v2) (vs 72 with MarshallerImpl)

testInternalCacheEntryMarshalling
  36(v1) -> 26(v2) (vs 25 with MarshallerImpl)

testSetMarshalling
  76(v1) -> 68(v2) (vs 58 with MarshallerImpl)

...etc

More to come...

Note that the failures in testBucketMarshalling and testMarshalledValueMarshalling are due to ISPN79 and ISPN-80.

> Add unit test that verifies number of written bytes
> ---------------------------------------------------
>
>                 Key: ISPN-59
>                 URL: https://jira.jboss.org/jira/browse/ISPN-59
>             Project: Infinispan
>          Issue Type: Sub-task
>          Components: RPC
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>             Fix For: 4.0.0.BETA1, 4.0.0.GA
>
>         Attachments: MarshallerTest.java, org.infinispan.marshall.MarshallersTest-v2-onlyobjecttable.xml, org.infinispan.marshall.MarshallerTest.xml
>
>
> Add written byte number comparisons to present  JBossMarshallerTest to make sure that it writes
> less bytes that existing MarshallerImpl and standard Java Serialization (ObjectStreamMarshaller)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira