2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-11-20 17:32:15 +00:00
Files
xcat-core/xCAT-test
Daniel Hilst 2efdce66b9 test(xcat-core): capture the missing xcat_t domain
xCAT ships no process domain. xcatd runs in unconfined_service_t, and a
client command runs in the domain of its caller, so no rule in the policy
module reaches either of them.

xcat_selinux_package.t now asserts the domain, the two entrypoint types,
the file contexts of the three entrypoints, the transition from systemd and
the transition from unconfined_t, and that no confined user domain gets a
transition. 9 of its 59 checks fail on this commit.

selinux_xcatd_domain asserts the live context of xcatd and its workers, and
the new selinux_client_domain case asserts the entrypoint labels and the
transition rules the loaded policy holds.

The two no-denial cases now count only the denials the kernel enforced,
because xcat_t is permissive and each access it needs is recorded. They also
pass --input-logs: on EL10 audit 4.0.3 ausearch reads the journal rather than
the file auditd.conf names, and answered "<no matches>" on a node whose log
held 1032 denials.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
2026-10-14 16:52:43 -03: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.