Changeset 1005


Ignore:
Timestamp:
01/28/26 13:17:04 (12 hours ago)
Author:
Kris Deugau
Message:

/branches/cname-collision

Test for correct handling and timestamp adjustment to new valid-after
overlapping an existing pending-expiry
See #72, #88

File:
1 edited

Legend:

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

    r1004 r1005  
    337337      }
    338338    };
     339    subtest 'valid before expiring record' => sub {
     340      $newname = 'valid-after2.expiry2.test';
     341      ($code, $msg) = $dnsdb->addRec('n', 'n', 5, \$newname, \$rectype, \$newval, 900, undef, 'f', $expirystamp);
     342      cmp_ok( $code, 'eq', 'WARN', "addRec() claimed failure" );
     343      if ($code eq 'WARN') {
     344        ($rcount) = $dbh->selectrow_array("SELECT count(*) FROM records WHERE domain_id = 5 AND host = '$newname' AND type <> 5");
     345        ok( $rcount == 1, " ... [$rcount] record(s) with $newname already exist" );
     346        like( $msg, qr/modified valid-after time;  conflicting expiring record found/, " ... returned matching error" );
     347      }
     348    };
    339349  };
    340350
Note: See TracChangeset for help on using the changeset viewer.