]> 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:22:07 +0000 (09:22 +0000)
commitba71be8ed163423808d1da05f08e9c116a3ce2e6
treedb80a1e122fc34b1a37c0a7b5bd31509811a5a96
parent3471c8a2b56c08e46dafa21dcd1e8f009d811b53
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").

(cherry picked from commit 4d08ec50d14deccb8d09eba8b56d7b7396144aac)
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]