45a3b53558
Fix logic to make sure we check if the refspec is of type `ostree://` even when it's explicitly specified. Also fix `Deploy` in the case where we didn't just `Download` the RPM diff by adding a new @checksum parameter to the higher-level API. Finally, add a basic test for the `GetCached*RpmDiff` APIs so we have at least *some* coverage. This is also good prep for making sure we don't break anything when we convert those APIs to use the more efficient pkglist metadata. The tests completely ignore the `DownloadRpmDiff` paths for now though. Closes: #1250 Closes: #1253 Approved by: cgwalters |
||
|---|---|---|
| .. | ||
| check | ||
| common | ||
| compose-tests | ||
| composedata | ||
| ex-container-tests | ||
| gpghome | ||
| manual | ||
| utils | ||
| vmcheck | ||
| compose | ||
| ex-container | ||
| README.md | ||
Tests are divided into three groups:
-
Tests in the
checkdirectory are non-destructive and uninstalled. Some of the tests require root privileges. Usemake checkto run these. -
The
composechecktests 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 installinside 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
Makefiletarget because it doesn't require building and doesn't use uninstalled binaries. -
Tests in the
vmcheckdirectory are oriented around using Vagrant. Usemake vmcheckto run them. See alsoHACKING.mdin the top directory.
The common directory contains files used by multiple
tests. The utils directory contains helper utilities
required to run the tests.