keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
2c94b11b68
rpm-ostree/tests
History
Jonathan Lebon 2c94b11b68 libvm: don't rsync $VMCHECK_INSTTREE 
We pretty standardized on insttree/ being the installation tree, and
we don't actually support $VMCHECK_INSTTREE anymore.

Closes: #1032
Approved by: cgwalters
2017-10-02 20:36:07 +00:00
..
check tests: Skip running introspection tests if built with ASAN 2017-09-24 13:32:00 +00:00
common libvm: don't rsync $VMCHECK_INSTTREE 2017-10-02 20:36:07 +00:00
compose-tests compose: Copy in additional files before postprocessing 2017-09-28 15:38:55 +00:00
composedata Add test infra for ex container, and one test for bash 2017-10-02 18:04:24 +00:00
ex-container-tests Add test infra for ex container, and one test for bash 2017-10-02 18:04:24 +00:00
gpghome daemon: start with one commit only when resolving versions 2016-12-24 12:28:48 +00:00
manual db: Remove query parameter to diff 2015-04-23 16:30:18 -04:00
utils daemon: Add a sanitycheck(/bin/true) before we deploy a tree 2017-07-27 17:58:58 +00:00
vmcheck libpriv/scripts: redirect scriptlet output to journal 2017-09-27 19:01:45 +00:00
compose Add test infra for ex container, and one test for bash 2017-10-02 18:04:24 +00:00
ex-container Add test infra for ex container, and one test for bash 2017-10-02 18:04:24 +00:00
README.md tests: Add ./tests/compose 2016-12-06 19:05:05 +00:00

README.md

Tests are divided into three groups:

  • Tests in the check directory are non-destructive and uninstalled. Some of the tests require root privileges. Use make check to run these.

  • The composecheck tests 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 install inside 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 Makefile target because it doesn't require building and doesn't use uninstalled binaries.

  • Tests in the vmcheck directory are oriented around using Vagrant. Use make vmcheck to run them. See also HACKING.md in the top directory.

The common directory contains files used by multiple tests. The utils directory contains helper utilities required to run the tests.