mirror of
https://github.com/xcat2/xcat-core.git
synced 2026-09-21 16:39:30 +00:00
Daniel Hilst
637d953d5a
ubuntu_subiquity_storage.t rewrites every /tmp/partitionfile redirect in the extracted block into a scratch tree, and bails out unless it rewrote exactly two. The number is the count of firmware branches the script had when the harness was written, so adding a branch stops the test rather than covering it. The guard now counts the branches it found and requires one redirect each, and fails separately if any path escaped the sandbox. It still bails out on a block with fewer than two branches, which would mean the extraction stopped matching. Still red on the PReP case of the previous commit: the block does not ask uname for the machine architecture yet. 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.