Skip to content

tests

Directory actions

More options

Directory actions

More options

Latest commit

 

History

History
 
 

tests

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
data
data
 
 
CMakeLists.txt
CMakeLists.txt
 
 
README.md
README.md
 
 
atconfig.in
atconfig.in
 
 
atlocal.in
atlocal.in
 
 
local.at
local.at
 
 
package.m4.in
package.m4.in
 
 
populate
populate
 
 
rpmbuild.at
rpmbuild.at
 
 
rpmbuildid.at
rpmbuildid.at
 
 
rpmconfig.at
rpmconfig.at
 
 
rpmconfig2.at
rpmconfig2.at
 
 
rpmconfig3.at
rpmconfig3.at
 
 
rpmconflict.at
rpmconflict.at
 
 
rpmdb.at
rpmdb.at
 
 
rpmdepmatch.at
rpmdepmatch.at
 
 
rpmdeps.at
rpmdeps.at
 
 
rpme.at
rpme.at
 
 
rpmgeneral.at
rpmgeneral.at
 
 
rpmi.at
rpmi.at
 
 
rpmio.at
rpmio.at
 
 
rpmmacro.at
rpmmacro.at
 
 
rpmorder.at
rpmorder.at
 
 
rpmpgp.at
rpmpgp.at
 
 
rpmpgpcheck.c
rpmpgpcheck.c
 
 
rpmpgppubkeyfingerprint.c
rpmpgppubkeyfingerprint.c
 
 
rpmpython.at
rpmpython.at
 
 
rpmquery.at
rpmquery.at
 
 
rpmreplace.at
rpmreplace.at
 
 
rpmscript.at
rpmscript.at
 
 
rpmsigdig.at
rpmsigdig.at
 
 
rpmspec.at
rpmspec.at
 
 
rpmtests.at
rpmtests.at
 
 
rpmvercmp.at
rpmvercmp.at
 
 
rpmverify.at
rpmverify.at
 
 
rpmvfylevel.at
rpmvfylevel.at
 
 

README.md

To run these tests, you need at least these dependencies on the host:

  1. fakechroot
  2. gdb
  3. gnupg >= 2.0

Then run the command

make check

The number of tests performed depends on features enabled at configure time, at least --with-/--without-lua and --enable-/--disable-python. See also the INSTALL file for more information.

To run single tests, you can run the commands:

make check TESTOPTS="$NNN $MMM"

where NNN and MMM are the numbers of the tests to be run.

You can also select tests by keywords used in their description by using the command:

 make check TESTOPTS="-k $KEYWORD"

Use multiple -k parameters to have tests with different keywords run. Use -k $KEYWORD1,$KEYWORD2 to execute tests matching both KEYWORD1 and KEYWORD2.

For all available options, see the output of the command:

./rpmtests --help

By default, tests are executed in parallel using all available cores, pass a specific -jN value to limit.