Two conflicts, both from xcat-core/#7978 landing on master. build-utils/lib/XCAT/BuildUtils.pm: both branches added a package_skip_reason, #7978 with a general @PACKAGE_SKIPS table and this branch with its own %EL_ONLY_PACKAGES and a second sub. git merges them as separate hunks because they sit apart in the file, and Perl takes the LAST definition, so keeping both silently deletes whichever rule came first. There is now one table and one sub. A rule names either the target prefixes that do NOT build the package, or, with `only`, the pattern of the targets that DO. The second form is what an EL-only package needs: naming the families that are not EL means a family added later tries to build it, which is how openSUSE reached xCAT-selinux and failed xcat-core-build-opensuse #42 on a missing selinux-policy-devel. buildrpms.pl: an empty build plan takes upstream's answer, a clean return rather than this branch's die. That is the decision #7978 exists for -- the dep pipeline asks for xCAT-genesis-base alone and no openSUSE target builds it -- so reinstating the die would fail a build that has nothing to do. selinux_el_only_scope.t is 37 of 37 and opensuse_no_legacy_genesis.t 22 of 22 on the merged tree, and the whole unit suite passes: 301 files, 9801 tests. 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.