From ebc6a9acec1cdc561b1ff994f379c5b208875f48 Mon Sep 17 00:00:00 2001 From: Michal Srb Date: Oct 12 2020 10:27:14 +0000 Subject: [generic_tests] Have one sentence per line --- diff --git a/modules/ROOT/pages/generic_tests.adoc b/modules/ROOT/pages/generic_tests.adoc index 0d90ed9..2b3a995 100644 --- a/modules/ROOT/pages/generic_tests.adoc +++ b/modules/ROOT/pages/generic_tests.adoc @@ -3,10 +3,12 @@ = Generic Tests = -Generic tests are tests that don't check only specific components (e.g. "dnf" or "kernel"), but can be typically applied to all artifacts of a certain type. An example of such a test could be a test that can be run on all RPM builds in a Bodhi update. +Generic tests are tests that don't check only specific components (e.g. "dnf" or "kernel"), but can be typically applied to all artifacts of a certain type. +An example of such a test could be a test that can be run on all RPM builds in a Bodhi update. -Fedora CI currently provides 3 generic tests. All of them run on packages that are being pushed to Rawhide via automatic Bodhi updates. +Fedora CI currently provides 3 generic tests. +All of them run on packages that are being pushed to Rawhide via automatic Bodhi updates. == rpmdeplint == @@ -23,7 +25,8 @@ This checks if all runtime dependencies of the given RPM packages would be satis check-repoclosure:: This is similar to check check-sat test, but check-repoclosure checks that all packages in the given repository that don't have any runtime dependency problems before the new packages are added, won't have any dependency problems after the packages are added to the repository. -Packages are only considered to be available for dependency resolution if they are the latest version and not obsoleted by any other package. Therefore this check can detect problems where a package under test is updating an existing package in the repository, but it no longer provides a requirement needed by some other package in the repository. +Packages are only considered to be available for dependency resolution if they are the latest version and not obsoleted by any other package. +Therefore this check can detect problems where a package under test is updating an existing package in the repository, but it no longer provides a requirement needed by some other package in the repository. Packages with pre-existing repoclosure problems are ignored. @@ -43,18 +46,21 @@ the file in this case); or [NOTE] ==== -Sometimes files can be owned by literally thousands of different packages. In order to properly check that there are no file conflicts, `rpmdeplint` would need to download all other packages. This would be very slow, so only a single other package is downloaded and checked. +Sometimes files can be owned by literally thousands of different packages. +In order to properly check that there are no file conflicts, `rpmdeplint` would need to download all other packages. +This would be very slow, so only a single other package is downloaded and checked. ==== check-upgrade:: Checks that there are no existing packages in the repositories which would upgrade or obsolete the given packages. -If this check fails, it means that the package under test will never be installed (since the package manager will always pick the newer or obsoleting package from the repositories instead) which is not desirable, assuming the package is intended as an update. +If this check fails, it means that the package under test will never be installed (since the package manager will always pick the newer or obsoleting package from the repositories instead) which is not desirable, assuming the package is intended as an update. == rpminspect == -RPM build deviation analysis tools. `rpminspect` looks at the output of an RPM build (e.g., the output of a Koji build) and examines the contents of the build artifacts to report: +RPM build deviation analysis tools. +`rpminspect` looks at the output of an RPM build (e.g., the output of a Koji build) and examines the contents of the build artifacts to report: * Policy compliance @@ -62,7 +68,8 @@ RPM build deviation analysis tools. `rpminspect` looks at the output of an RPM b * General correctness and best practices -`rpminspect` performs more than 30 different checks on packages. To list all of them, with a nice description, please run `rpminspect -v -l`. +`rpminspect` performs more than 30 different checks on packages. +To list all of them, with a nice description, please run `rpminspect -v -l`. == installability ==