Changeset 1031


Ignore:
Timestamp:
02/06/26 12:59:37 (4 days ago)
Author:
Kris Deugau
Message:

/branches/cname-collision

Test with updating to a valid-after CNAME:
Add test for collision with existing valid-after record, new timestamp after existing
See #72, #88

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/cname-collision/t/cname.t

    r1030 r1031  
    570570      }
    571571    };
     572    subtest 'valid after active valid-after record' => sub {
     573      $newname = 'validafter5a.expiry3.test';
     574      ($code, $msg) = $dnsdb->updateRec('n', 'n', 104, 6, \$newname, \$rectype, \$newval, 900, undef, 'f', $expirystamp);
     575      cmp_ok( $code, 'eq', 'FAIL', "updateRec() claimed failure" );
     576      if ($code eq 'FAIL') {
     577        ($rcount) = $dbh->selectrow_array("SELECT count(*) FROM records WHERE domain_id = 6 AND host = '$newname'");
     578        ok( $rcount == 1, " ... [$rcount] correct number of records for $newname" );
     579        like( $msg, qr/non-CNAME records with timestamps already exist/, " ... returned matching error" );
     580      }
     581    };
    572582  }; # update to valid-after CNAME
    573583
Note: See TracChangeset for help on using the changeset viewer.