run_genesis in xCAT-test/bats/helpers/genesis_sandbox.bash compared the status of "timeout 20 /bin/bash /run/script" with one exact number. GNU coreutils timeout reports a child that a signal killed as 128+signal, so genesis_discovery_uuid.bats expects 143 for SIGTERM. The uutils coreutils of Ubuntu 26.04 reports the signal number alone, 15, so the same outcome fails the assertion there. run_genesis now accepts the expected status or, when that status is above 128, the signal number alone. A caller that expects 0 keeps one accepted value, and an unrelated failure is still a failure. The comment names the two conventions. Evidence: a four-case bats file drives run_genesis with a controlled status. With the change, 143 and 15 both pass against an expected 143, while status 1 against 143 and status 15 against 0 still fail. Without the change only the 15 case flips to "Expected exit 143, got 15"; the control and both discriminators are unchanged. The five "= 143" comparisons in genesis_openembedded_runtime.bats stay as they are: terminate_after reads its status from the bash wait builtin, which computes 128+signal itself and does not call timeout. 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.