mirror of
https://github.com/xcat2/xcat-core.git
synced 2026-09-21 16:39:30 +00:00
Daniel Hilst
57dddd4efd
xcat_riscv64_genesis_dependency.t pins the deb dependency on the legacy Genesis scripts as a single xcat-genesis-scripts-amd64 entry qualified [!riscv64]. That entry gives a ppc64el management node the amd64 scripts package, which pulls the amd64 Genesis base with it, and this branch replaces it with one entry per architecture. The test now asserts that every xcat-genesis-scripts entry names an architecture that has a legacy Genesis, and that the ppc64el reduction asks for xcat-genesis-scripts-ppc64el. The riscv64 assertions are unchanged: no entry applies there. 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 |
| 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.
See unit/README.md and bats/README.md for the detailed rules for
each unit-test suite.