e6e8c607c2
* test/README: Improve wording, convert to markdown |
||
---|---|---|
.. | ||
data | ||
Makefile.am | ||
README.md | ||
atlocal.in | ||
debugedit.at | ||
local.at | ||
rpmbuild.at | ||
rpmbuildid.at | ||
rpmconfig.at | ||
rpmconfig2.at | ||
rpmconfig3.at | ||
rpmconflict.at | ||
rpmdb.at | ||
rpmdepmatch.at | ||
rpmdeps.at | ||
rpmgeneral.at | ||
rpmi.at | ||
rpmio.at | ||
rpmmacro.at | ||
rpmorder.at | ||
rpmpython.at | ||
rpmquery.at | ||
rpmreplace.at | ||
rpmscript.at | ||
rpmsigdig.at | ||
rpmspec.at | ||
rpmtests.at | ||
rpmvercmp.at | ||
rpmverify.at | ||
rpmvfylevel.at |
README.md
To run these tests, you need at least these dependencies on the host:
- fakechroot
- gdb
- 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 populate_testing && ./rpmtests $NNN $MMM ...
where NNN and MMM are the numbers of the tests to be run.
To get the list of available tests, use the command:
./rpmtests -l
You can also select tests by keywords used in their description by using the command:
./rpmtests -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.
See the output of the command:
./rpmtests --help
for more options. But be aware some (like -j
) need not work properly with
the test suite unless a very restricted set of test is run.