Vinícius Ferrão
bf5e2bdb20
The packet test runs dhcpd and kea-dhcp4 in a network namespace with the rules that BootPolicy renders, and sends relayed DHCPDISCOVER packets from a second namespace. It checks the boot file of firmware PXE, xNBA and iPXE clients, with each iPXE feature present or missing, for an xnba node and an ipxe node that install, for both methods with a SAN disk, and for an unknown node. On ISC it also covers an iSCSI node of each method in the boot state, and repeats the node rows after a restart, when dhcpd reads the host statements back from dhcpd.leases. On Kea it repeats the rows of the ipxe nodes with a configuration that makedhcp upgraded, which keeps the xNBA global classes of the older makedhcp -n. It also checks that the UEFI clients of an xnba node get xNBA when the server lacks the xNBA UEFI file. The Kea validation test checks the x86 classes of xnba and ipxe nodes with kea-dhcp4 -t. XCAT::Test::DHCP builds the packets, and the integration case expects seven files.
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 |
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.