2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-10-21 15:18:19 +00:00
Files
xcat-core/xCAT-test/bats
2026-10-09 21:01:26 -03:00
..

xCAT-test/bats

Shell-script unit tests live here and run with:

bats -r xCAT-test/bats

The GitHub Actions xcat_test workflow runs this command after the Perl .t unit tests. Use BATS for shell behavior that can be exercised from the source tree without an installed xCAT, a live management node, or real services.

Prefer sourcing an existing shell library or sourceable script and calling the function under test. Keep reusable install-template helpers in xCAT-server/share/xcat/install/scripts/scriptlib, and reusable postscript helpers in xCAT/postscripts/xcatlib.sh. Use scratch directories and shadowed commands so tests cannot write to the host.

Extraction helpers in helpers/shell_source.bash are only for legacy code that cannot safely be sourced yet. Do not add Perl .t tests that grep shell source when the behavior can be tested with BATS.

Postscript sandbox prerequisites

otherpkgs_upgrade_scope.bats and routeop.bats run complete postscripts in Linux filesystem and network namespaces. Their /etc writes stay inside test fixtures. They require Bubblewrap, Bash, GNU core utilities, grep, sed, and permission to create user namespaces. The CI workflow installs Bubblewrap and enables those namespaces.

Missing prerequisites fail these tests without stopping unrelated test files. Non-Linux hosts report a skip. Set TMPDIR to a writable, executable filesystem if the default temporary directory is mounted with noexec.

go_xcat_os_release.bats and the full-script cases in postscripts_apt_get.bats use the same namespace isolation. They require bats-core 1.4 or newer. OS detection also requires GNU awk for the legacy Red Hat release parser. Postscript cases require GNU diffutils.

go_xcat_os_release.bats and go_xcat_el_repo_check.bats source the complete go-xcat script. OS detection uses mawk when available, otherwise the host AWK. The two legacy Red Hat version cases use GNU awk. CI installs both interpreters. Package-manager commands are test doubles, so these cases check selection, arguments and error handling, not repository availability or package installation.