Re: [infinispan-dev] Raison de etre of TestObjectStreamMarshaller

Manik Surtani wrote: > Yes, it was for ease of debugging, and also to isolate the cause of > problems. I think we should stick with the Test marshaller for > such purposes, even if purely for the sake of component isolation > during testing. Ok. > As for the coverage issues re: the VAM, there should be a separate > set of unit tests for the VAM to ensure every known type is > properly marshalled and unmarshalled by the VAM. I built a similar test for JBoss Marshaller called JBossMarshallerTest. It know uses VAM rather than JBossMarshaller, so that's effectively it. I need to double check whether all types are now covered and I'll refactor it to better show it's job now.