NFD » ndn-tools

I suggest having at least these test cases:

• prepare Data, sign as default, reply to Interest
• prepare Data with FinalBlockId, sign as default, reply to Interest
• prepare Data with FreshnessPeriod set to a positive value, sign as default, reply to Interest
• prepare Data with FreshnessPeriod set to zero, sign as default, reply to Interest
• prepare Data, sign with DigestSha256, reply to Interest
• prepare Data, sign with specified identity, reply to Interest
• prepare Data, sign as default, wait for specified timeout, Interest doesn't arrive
• prepare Data, send Data without waiting for Interest
• Data size exceeds MAX_NDN_PACKET_SIZE

I agree with note-2, except that I don't think we need to distinguish between FreshnessPeriod > 0 and FreshnessPeriod == 0. There's no conditional in ndnpoke that would be affected by that. Just do one test with a specified FreshnessPeriod (i.e. >= 0).

Hi,
what does the ninth test case compare? "Data size exceeds MAX_NDN_PACKET_SIZE"
Can someone clarify?

Data size exceeds MAX_NDN_PACKET_SIZE

If size of the prepared Data packet exceeds the practical limit of NDN packet size, ndnpoke should quit with an appropriate error, and must not send this Data packet.

Thanks, also one more thing-- test case 6 "prepare Data, sign with specified identity, reply to Interest"

What is the specified identity?

prepare Data, sign with specified identity, reply to Interest

This is equivalent to command dd if=/dev/urandom bs=4K count=1 | ndnpoke -i /identity /A/$RANDOM.

What is the specified identity?

“/identity” in the example above.

How would I provide input to ndnpoke for the data packet content?

Have you looked at the (now abandoned) change mentioned above? You should probably resume from there rather than start from scratch.

How would I provide input to ndnpoke for the data packet content?

The NdnPoke class needs to accept a parameter of type std::istream& through which the packet payload can be read. main() will pass std::cin, while in the unit tests you can pass whatever, e.g. an instance of std::stringstream containing the test data.