Changeset 984 for branches/cname-collision/t/cname.t

Timestamp:

01/15/26 11:29:54 (5 days ago)

Author:

Kris Deugau

Message:

/branches/cname-collision

Added specific test for CNAME colliding with a record that has a valid-after
timestamp in the past.

• additional test record
• adjusted timestamp-retrieval SQL
• extend logic tree for this case

See #72, #88

File:

• branches/cname-collision/t/cname.t (modified) (2 diffs)

branches/cname-collision/t/cname.t

@@ -226 +226 @@
       }
     };
-    subtest '  - collision with active-after record' => sub {
+    subtest '  - collision with pending active-after record' => sub {
       $newname = 'active-after1.expiry1.test';
       ($code, $msg) = $dnsdb->addRec('n', 'n', 4, \$newname, \$rectype, \$newval, 900);
@@ -243 +243 @@
       }
     };
+    subtest '  - collision with active active-after record' => sub {
+      $newname = 'active-after2.expiry1.test';
+      ($code, $msg) = $dnsdb->addRec('n', 'n', 4, \$newname, \$rectype, \$newval, 900);
+      ok( $code eq 'FAIL', "addRec() claimed failure" );
+      if ($code eq 'FAIL') {
+        ($rcount) = $dbh->selectrow_array("SELECT count(*) FROM records WHERE domain_id = 4 AND host = '$newname' AND type <> 5");
+        ok( $rcount == 1, " ... [$rcount] record(s) with $newname already exist" );
+        like( $msg, qr/record with a valid-after time in the past/, " ... returned matching error" );
+      }
+    };
   }; # add non-timestamp CNAME