keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
80de17623f
rpm-ostree/tests
History
Colin Walters 80de17623f tests/livefs: Make sure /usr/bin/ls is executable 
Oh man was I confused how this happened; thought it was a bug in some livefs
changes I was working on.

Closes: #995
Approved by: jlebon
2017-09-15 19:10:24 +00:00
..
check daemon/upgrader: make use of override-commit-ids 2017-09-12 17:23:25 +00:00
common libvm: set up ControlPath socket in /var/tmp 2017-08-24 22:12:17 +00:00
compose-tests Rework treecompose kernel processing 2017-09-12 14:26:44 +00:00
composedata ci: unite testsuites and run vmcheck on centos 2017-07-18 13:58:38 +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 tests/livefs: Make sure /usr/bin/ls is executable 2017-09-15 19:10:24 +00:00
compose tests/compose: Add env variables to force caching and fast fail 2017-09-12 14:26:44 +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.