Vinícius Ferrão
8816ea47f1
The test packs cpio and tar archives with gzip, xz and pigz, and squashfs images, on the Red Hat path. A wrapper around the compressor, mksquashfs, cpio or find records the file under the final name while the pack runs, and then runs the real tool or fails. It checks that nodes get the previous archive during the pack, that a pack whose compressor, cpio or file listing fails keeps the previous archive, metainfo and other formats, that a successful pack replaces them, and that no temporary file is left. The next pack removes a temporary file or directory that an interrupted pack on the same host left, and keeps one that another host is writing. For a StateLite tree, it checks that a pack that fails while listing the files, compressing them or creating the temporary directory restores the files that packimage switched, and that a retry keeps them. When a file cannot be moved back, the original and the previous archive must stay, and the next pack must refuse to run. A pack must wait while another host holds .packimage-publish. When a pack that did not finish left the lock, the next pack must fail, name the holder, and keep the previous archive and the lock. With --tracker, ctorrent must build the metainfo from the new archive under its final name before the archive is replaced. A ctorrent failure must keep the previous archive and metainfo, and so must a previous metainfo that cannot be removed.
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.