From 2ef92ca0ee271988e02d48890facdd79778de91b Mon Sep 17 00:00:00 2001 From: Denys Fedoryshchenko Date: Wed, 28 Oct 2026 20:16:22 +0200 Subject: docs: distinguish historical safeguard validation from current test limits Signed-off-by: Denys Fedoryshchenko --- tests/README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'tests') diff --git a/tests/README.md b/tests/README.md index 566d760c..870cf8c8 100644 --- a/tests/README.md +++ b/tests/README.md @@ -15,6 +15,22 @@ sh tests/unit/run_safeguards.sh build log_line These tests do not require installed kernel modules or root privileges. The sanitizer runtime needs an environment that permits its process inspection. +The runner has six suites: `dhcpv6`, `radius`, `vrf`, `lcp`, `mempool`, and +`log_line`. With no names it attempts all six. The DHCPv6 fixture currently +refers to the removed `conf_dns_count` variable, and the runner does not link +the `ipv6_dns.c` implementation now used by the reply builder. That fixture +and its build command must be updated before a full run can pass. + +The other five suites can be run explicitly while that regression is being fixed: + +```bash +sh tests/unit/run_safeguards.sh build radius vrf lcp mempool log_line +``` + +A successful subset run does not validate the DHCPv6 safeguards. The +[integration validation record](../docs/ng40-safeguards-review.md#validation) +describes results from the revision at which those safeguards were introduced. + ## Kernel module installation test The kernel module installation regression test is rootless and does not need -- cgit v1.2.3