keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
c5fa202378
rpm-ostree/tests
History
Jonathan Lebon c5fa202378 sync.sh: tweak for container workflow 
In the container build + vagrant test workflow, we have to run `make
vmsync` from the env in which autoconf was run, which is the container.

However, when using git worktrees (which is useful in this scenario to
avoid having to overwrite your local builds) and a CentOS build
container, the git inside is too old to understand worktrees, so let's
avoid invoking git in any of the test harness scripts.

Also make sure to restorecon after installing the new rpm-ostreed.

Closes: #555
Approved by: cgwalters
2016-12-21 20:00:43 +00:00
..
check test-basic.sh: add test for bad out-of-branch deploy 2016-10-20 14:06:58 +00:00
common libvm.sh: strengthen reboot 2016-12-07 21:47:58 +00:00
compose-tests compose-tests: add more tests 2016-12-09 16:18:11 +00:00
composedata tests: Add ./tests/compose 2016-12-06 19:05:05 +00:00
manual db: Remove query parameter to diff 2015-04-23 16:30:18 -04:00
utils Redo vmcheck to abstract over ssh-config, drop all building 2016-11-16 18:14:23 +00:00
vmcheck sync.sh: tweak for container workflow 2016-12-21 20:00:43 +00:00
compose compose-tests: add more tests 2016-12-09 16:18:11 +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.