1dc7503838
This is a major downside of reworking and generating new CI flows, it's super easy to lose testing what you intend to. Also, we clearly need to figure out a flow where this is shared across repos, since I don't want to copy-paste this into e.g. ostree too. That's https://github.com/coreos/fedora-coreos-tracker/issues/263 |
||
|---|---|---|
| .. | ||
| check | ||
| common | ||
| compose | ||
| gpghome | ||
| kolainst | ||
| manual | ||
| utils | ||
| vmcheck | ||
| compose.sh | ||
| README.md | ||
| runkola | ||
| vmcheck.sh | ||
Tests are divided into three groups:
-
Tests in the
checkdirectory are non-destructive and uninstalled. Some of the tests require root privileges. Usemake checkto run these. -
The
composechecktests currently require uid 0 capabilities - the default in Docker, or you can run them via a user namespace. They are non-destructive, but are installed.To use them, you might do a
make && sudo make installinside a Docker container.Then invoke
./tests/compose. Alternatively of course, you can simply run the tests on a host system or in an existing container, without doing a build.Note: This is intentionally not a
Makefiletarget because it doesn't require building and doesn't use uninstalled binaries. -
Tests in the
vmcheckdirectory are oriented around using Vagrant. Usemake vmcheckto run them. See alsoHACKING.mdin the top directory.
The common directory contains files used by multiple
tests. The utils directory contains helper utilities
required to run the tests.