keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
2232edb6b0
rpm-ostree/tests
History
Rafael Fonseca cac5aa413d app,daemon: Use public libostree's kargs API 
This deduplicates the code between the two repositories.

Closes: #1862

Signed-off-by: Rafael Fonseca <r4f4rfs@gmail.com>
2019-08-21 16:47:52 -04:00
..
check app,daemon: Use public libostree's kargs API 2019-08-21 16:47:52 -04:00
common tests/vmcheck: Fully drop python 3 requirement 2019-06-10 15:36:06 +00:00
compose-tests postprocess: Quote OSTREE_VERSION value 2019-07-25 07:44:43 +00:00
composedata treefile: Add new add-commit-metadata key 2019-07-09 20:28:18 +00:00
ex-container-tests ci: Bump to f29 2019-03-19 12:19:38 +00:00
gpghome daemon: start with one commit only when resolving versions 2016-12-24 12:28:48 +00:00
manual tests: Bump to Python 3 only 2019-05-08 19:02:32 +00:00
utils tests: Bump to Python 3 only 2019-05-08 19:02:32 +00:00
vmcheck app/deploy: Add --disallow-downgrade switch 2019-08-21 16:43:37 -04:00
compose compose: Add --download-only-rpms 2019-03-25 14:33:17 +00:00
ex-container ci: Fix ex-container LOGDIR 2019-03-19 12:19:38 +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.