keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
c6e5e80d94
rpm-ostree/tests
History
Jonathan Lebon c6e5e80d94 vmcheck: Work around read-only /sysroot 
We need to adapt some of our tests here which assume that `/sysroot` is
writable. However, in FCOS this is no longer the case now that we enable
`sysroot.readonly`.

We only remount rw for the couple of operations that need it so that we
still retain coverage for the ro path everywhere else.
2020-03-19 16:24:04 +01:00
..
check
common vmcheck: Work around read-only /sysroot 2020-03-19 16:24:04 +01:00
compose treefile: Add exclude-packages 2020-02-05 21:02:06 +01:00
ex-container-tests
gpghome
manual
utils
vmcheck vmcheck: Work around read-only /sysroot 2020-03-19 16:24:04 +01:00
compose.sh tests/compose: Stop freezing on specific FCOS commit 2020-02-27 04:50:59 +01:00
ex-container
README.md tests: Add ./tests/compose 2016-12-06 19:05:05 +00:00
vmcheck.sh tests/compose: Target FCOS 31, move off of PAPR 2020-01-08 16:42:54 +01: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.