On 6/17/2012 10:07 AM, Bryan Pendleton wrote:
Hello Nufail,
I think that these methods are going to be challenging to exercise, since
they may only arise due to implementation errors in either the client or
the server.
We have a special test suite that we have used in the past to force the
execution of code paths such as these. You can find that test suite here:
java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/ProtocolTest.java
and its test data is located here:
java/testing/org/apache/derbyTesting/functionTests/tests/derbynet/protocol.tests
As a first step, you could try running the ProtocolTest test suite with
code coverage enabled, just to confirm that it doesn't currently exercise
these particular methods in NetConnectionReply.
I believe with ProtocolTest the client is not invoked at all but rather
replaces the client, so it can only be used to help cover server side
code. I put some more details in my response to this thread.
