]> git.ipfire.org Git - thirdparty/bind9.git/commit
Move rollover test cases to separate test dir
authorMatthijs Mekking <matthijs@isc.org>
Fri, 28 Feb 2025 14:52:20 +0000 (15:52 +0100)
committerMatthijs Mekking <matthijs@isc.org>
Mon, 2 Jun 2025 09:21:06 +0000 (09:21 +0000)
commit4d08ec50d14deccb8d09eba8b56d7b7396144aac
tree9d079e1b7b9946b56f346b1fae5a9e5b2ed72a08
parentead7b480034b1fb37d5b51136785ca9c4a182f79
Move rollover test cases to separate test dir

In order to keep the kasp system test somewhat approachable, let's
move all rollover scenarios to its own test directory. Starting with
the manual rollover test cases.

A new test function is added to 'isctest.kasp', to verify that the
relationship metadata (Predecessor, Successor) is set correctly.

The configuration and setup for the zone 'manual-rollover.kasp' are
almost copied verbatim, the only exception is the keytimes. Similar
to the test kasp cases, we no longer set "SyncPublish/PublishCDS" in
the setup script. In addition to that, the offset is changed from one
day ago to one week ago, so that the key states match the timing
metadata (one day is too short to move a key from "hidden" to
"omnipresent").
bin/tests/system/Makefile.am
bin/tests/system/kasp/ns3/named-fips.conf.in
bin/tests/system/kasp/ns3/policies/kasp-fips.conf.in
bin/tests/system/kasp/ns3/setup.sh
bin/tests/system/kasp/tests.sh
bin/tests/system/rollover/ns3/kasp.conf.j2 [new file with mode: 0644]
bin/tests/system/rollover/ns3/named.conf.j2 [new file with mode: 0644]
bin/tests/system/rollover/ns3/setup.sh [new file with mode: 0644]
bin/tests/system/rollover/ns3/template.db.in [new file with mode: 0644]
bin/tests/system/rollover/setup.sh [new file with mode: 0644]
bin/tests/system/rollover/tests_rollover.py [new file with mode: 0644]