The assertions added with this test required Socket6 and IO::Socket::INET6 on every RPM family, which contradicts xcat_server_inet6_optional_dependency.t and the reason it records: every call site loads the modules with an eval and keeps working on IPv4, so a hard dependency states a dependency the code does not have. The measurement that prompted the test still holds, and it is narrower than it looked. Both modules are absent on a Leap 15.6 management node because the openSUSE Minimal-VM image sets solver.onlyRequires = true in /etc/zypp/zypp.conf, so zypper installs no recommended package. dnf installs one, so EL and openEuler need no hard dependency. The test now reads requires and recommends separately per family: openSUSE requires both and recommends neither, EL and openEuler recommend both and require neither. The deb control files are read per package, since perl-xCAT has carried a hard dependency since before this rule. xcat_server_inet6_optional_dependency.t gains a pointer to the openSUSE exception so the two files do not disagree in prose. 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.