bind9/bin/tests/system/upforwd/tests_sh_upforwd.py
Mark Andrews afc4413862 Handle example3.db being modified in upforwd system test
The zone file for example3 (ns1/example3.db) can be modified in the
upforwd test as example3 is updated as part of the test.  Whether
the zone is written out or not by the end of the test is timing
dependent.  Rename ns1/example3.db to ns1/example3.db.in and copy
it to ns1/example3.db in setup so we don't trigger post test changes
checks.
2025-02-25 12:28:58 +11:00

38 lines
949 B
Python

# Copyright (C) Internet Systems Consortium, Inc. ("ISC")
#
# SPDX-License-Identifier: MPL-2.0
#
# This Source Code Form is subject to the terms of the Mozilla Public
# License, v. 2.0. If a copy of the MPL was not distributed with this
# file, you can obtain one at https://mozilla.org/MPL/2.0/.
#
# See the COPYRIGHT file distributed with this work for additional
# information regarding copyright ownership.
import pytest
pytestmark = pytest.mark.extra_artifacts(
[
"Ksig0.example2*",
"dig.out.*",
"dnstap.out.*",
"dnstapread.out*",
"keyname*",
"nsupdate.out.*",
"ans*/ans.run",
"ns*/*.bk",
"ns*/*.jnl",
"ns1/example.db",
"ns1/example2-toomanykeys.db",
"ns1/example2.db",
"ns1/example3.db",
"ns3/dnstap.conf",
"ns3/dnstap.out",
"ns3/noprimary1.db",
]
)
def test_upforwd(run_tests_sh):
run_tests_sh()