From: JINMEI Tatuya Date: Wed, 8 Feb 2012 18:01:13 +0000 (-0800) Subject: [1570] updated test comments for clarification. X-Git-Tag: trac2351_base~263^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=63f7b1ab7c81110633ed2e381e5fdfe05e143d72;p=thirdparty%2Fkea.git [1570] updated test comments for clarification. --- diff --git a/src/bin/auth/tests/query_unittest.cc b/src/bin/auth/tests/query_unittest.cc index 87017673ea..8a3374304e 100644 --- a/src/bin/auth/tests/query_unittest.cc +++ b/src/bin/auth/tests/query_unittest.cc @@ -1804,11 +1804,13 @@ TEST_F(QueryTest, dsAtGrandParent) { ns_addrs_and_sig_txt.c_str()); } -// DS query for a "grandchild" zone, and the server has authority of the -// child zone, too. In this case the query should be handled in the child -// side and should result in no data with SOA. +// DS query sent to a "grandparent" server that also has authority for the +// child zone. In this case the query should be handled in the child +// side and should result in no data with SOA. Note that the server doesn't +// have authority for the "parent". Unlike the dsAboveDelegation test case +// the query should be handled in the child zone, not in the grandparent. TEST_F(QueryTest, dsAtGrandParentAndChild) { - // Pretending to have authority for the grandchild zone, too. + // Pretending to have authority for the child zone, too. const Name childname("grand.delegation.example.com"); memory_client.addZone(ZoneFinderPtr( new AlternateZoneFinder(childname)));