This branch is titled "provision a node over IPv6" and shipped one IPv6 xcattest case, makenetworks_ipv6_route_filter_unit, which is a unit-style check that no bundle names. Nothing ran against a management node to show that the DHCPv6 path works. makedhcp_dhcpv6_boot_intent builds its own state on the management node -- an IPv6 address on the provisioning NIC, a matching xCAT network, and a node that answers only on IPv6 with a fixed vpd.uuid -- and asserts four things a UEFI client depends on: makedhcp exits 0, kea-dhcp6 accepts the configuration it wrote, the reservation's DUID is the uuid with its first three fields reversed as the firmware sends them, and the bootfile-url is the RFC 5970 form with a bracketed authority. It then asserts the IPv4 configuration carries no reservation and no client class for that node. Every value is read out of Kea's JSON with python3 and compared for EQUALITY. A grep for bootfile-url passes on the key alone, and a check whose pattern appears in its own command cannot fail. The uuid is fixed rather than generated, because the expected DUID is derived from it. The case pre-cleans before it builds: xcattest stops a case at its first failed check, so the cleanup at the end does not run after a failure, and without the pre-clean a failed run would leave an address, a network and a node behind for the next run to measure. It needs no compute node and no image, so it runs wherever a management node is installed. ci/bundles/ipv6_dhcpv6.bundle and the el10-x86_64-ipv6 cell in xcat-core-ci-cd dispatch it. Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
xCAT-test
Unit tests that run from the source checkout are split by implementation language:
| Test type | Location | Runner |
|---|---|---|
| Perl unit tests | xCAT-test/unit/*.t |
prove -r xCAT-test/unit |
| Shell unit tests | xCAT-test/bats/*.bats |
bats -r xCAT-test/bats |
| Black-box service tests | xCAT-test/blackboxtest/ |
python3 -m unittest discover -s tests, then blackboxtest run <conf> on a management node |
| Native host tests | xCAT-test/native/*.t, xCAT-test/native/*.bats |
Selected CI cases and explicit lab runs; see native/README.md |
| CLI functional tests | xCAT-test/autotest/testcase/ and xCAT-test/autotest/bundle/ |
xcattest -f <cluster.conf> -t <case> or xcattest -f <cluster.conf> -b <bundle> |
Use Perl .t tests for Perl modules, Perl scripts, templates, and repository
artifacts. Use BATS tests for shell-script behavior that can be exercised from
the checkout by sourcing a shell library or script and shadowing external
commands.
Shell behavior should not be tested by Perl tests that grep shell source. Put
those tests under xCAT-test/bats instead.
blackboxtest is the odd one out: its Python unit tests and blackboxtest validate run offline like the others, but its point is the third column --
asking a management node what a booting node asks (DHCP, DNS, TFTP, HTTP,
xcatd) and asserting on the answers. It talks to the services only as a client,
so it does not depend on which DHCP server answers or on the xCAT database.
See unit/README.md, bats/README.md and blackboxtest/README.md for the
detailed rules for each suite.