From: JINMEI Tatuya Date: Tue, 27 Nov 2012 21:29:39 +0000 (-0800) Subject: [2420] fixed typo in test names X-Git-Tag: bind10-1.0.0-beta-release~52^2~1^2~2^2~3 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=c42c6b938afa4e77d8b0545f1b2dbd335c9d3890;p=thirdparty%2Fkea.git [2420] fixed typo in test names --- diff --git a/src/lib/datasrc/tests/memory/zone_data_updater_unittest.cc b/src/lib/datasrc/tests/memory/zone_data_updater_unittest.cc index 60b942b0ab..22ee9d9c3c 100644 --- a/src/lib/datasrc/tests/memory/zone_data_updater_unittest.cc +++ b/src/lib/datasrc/tests/memory/zone_data_updater_unittest.cc @@ -85,7 +85,7 @@ getNode(isc::util::MemorySegment& mem_sgmt, const Name& name, return (node); } -TEST_F(ZoneDataUpdaterTest, rrisgOnly) { +TEST_F(ZoneDataUpdaterTest, rrsigOnly) { // RRSIG that doesn't have covered RRset can be added. The resulting // rdataset won't have "normal" RDATA but sig RDATA. updater_.add(ConstRRsetPtr(), textToRRset( @@ -143,7 +143,7 @@ TEST_F(ZoneDataUpdaterTest, rrisgOnly) { EXPECT_FALSE(zone_data_->isSigned()); } -// Commonly used checks for rrisgForNSEC3Only +// Commonly used checks for rrsigForNSEC3Only void checkNSEC3Rdata(isc::util::MemorySegment& mem_sgmt, const Name& name, ZoneData* zone_data) @@ -158,7 +158,7 @@ checkNSEC3Rdata(isc::util::MemorySegment& mem_sgmt, const Name& name, EXPECT_EQ(1, rdset->getSigRdataCount()); } -TEST_F(ZoneDataUpdaterTest, rrisgForNSEC3Only) { +TEST_F(ZoneDataUpdaterTest, rrsigForNSEC3Only) { // Adding only RRSIG covering NSEC3 is tricky. It should go to the // separate NSEC3 tree, but the separate space is only created when // NSEC3 or NSEC3PARAM is added. So, in many cases RRSIG-only is allowed,