keremet/rpm-ostree
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
1c17e93029
rpm-ostree/tests
History
Jonathan Lebon 853737f667 unpacker: encode NEVRA info in commit metadata 
It seems silly that to find out more detailed information about the
NEVRA of a cached pkg, we have to resort to write out the header to
disk, then reading it back in with librpm in order to tease out the info
we want. Let's just encode that information directly in the commit
metadata and provide a helper to fetch it.

Closes: #847
Approved by: cgwalters
2017-06-23 17:47:22 +00:00
..
check unpacker: encode NEVRA info in commit metadata 2017-06-23 17:47:22 +00:00
common vmcheck: add new test for override remove 2017-06-05 20:48:50 +00:00
compose-tests compose: Add tmp-is-dir option to make /tmp a directory 2017-05-24 17:49:36 +00:00
composedata compose: use test env fedora.repo file instead 2017-05-30 14:17: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 ci: Build ostree from git temporarily 2017-03-27 16:35:43 +00:00
vmcheck override remove: allow inactive removals 2017-06-20 21:24:05 +00:00
compose compose: use test env fedora.repo file instead 2017-05-30 14:17: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.