2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-11-21 18:02:18 +00:00
Files
xcat-core/xCAT-test
Daniel Hilst 7332309040 fix(xcat-core): three paths the file contexts get wrong
The wrapper /opt/xcat/bin/genimage carried the image entrypoint, so a
command that writes a request to the socket ran with the authority to
relabel every type. It is now a client. The build still reaches
xcat_image_t: the plugin, and the --interactive mode of the wrapper, run the
per-OS program through a shell, and that exec transitions from either caller
domain.

The per-OS geninitrd gets its own line, because most of those names are
symlinks to their sibling genimage but netboot/fedora12/geninitrd is a real
program, and the genimage glob never matches it.

/opt/xcat/bin/xcatDBcmds is labelled as a client. It is the third
dispatcher, reached by 12 symlinks including lsdef, chdef, mkdef and rmdef,
and without this they ran in the caller's domain while rpower ran in xcat_t.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-15 16:23:54 -03:00
..
2018-04-26 15:15:47 -04:00

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.