test/README: Improve wording, convert to markdown (#1662)
* test/README: Improve wording, convert to markdown
This commit is contained in:
parent
3c26b1c701
commit
e6e8c607c2
|
@ -3,7 +3,7 @@
|
|||
include $(top_srcdir)/rpm.am
|
||||
AM_CFLAGS = @RPMCFLAGS@
|
||||
|
||||
EXTRA_DIST =
|
||||
EXTRA_DIST = README.md
|
||||
CLEANFILES =
|
||||
|
||||
##
|
||||
|
|
36
tests/README
36
tests/README
|
@ -1,36 +0,0 @@
|
|||
To run these tests you need at least these dependencies on the host:
|
||||
|
||||
fakechroot (https://github.com/dex4er/fakechroot/wiki)
|
||||
gdb (https://www.gnu.org/software/gdb/)
|
||||
gnupg >= 2.0 (https://www.gnupg.org/)
|
||||
|
||||
Then run
|
||||
|
||||
make check
|
||||
|
||||
The number of tests performed depends on enabled features 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
|
||||
|
||||
make populate_testing ; ./rpmtests NNN MMM ...
|
||||
|
||||
where NNN and MMM are the numbers of the tests to be run. Use
|
||||
|
||||
./rpmtests -l
|
||||
|
||||
to get the list of available tests.
|
||||
You can also select tests by keywords used in their description by using
|
||||
|
||||
./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
|
||||
|
||||
./rpmtests --help
|
||||
|
||||
for more options. But be aware some (like -j) may not work properly with
|
||||
the test suite unless a very restricted set of test is run.
|
|
@ -0,0 +1,37 @@
|
|||
To run these tests, you need at least these dependencies on the host:
|
||||
|
||||
1. [fakechroot](https://github.com/dex4er/fakechroot/wiki)
|
||||
1. [gdb](https://www.gnu.org/software/gdb/)
|
||||
1. [gnupg](https://www.gnupg.org/) >= 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](../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.
|
Loading…
Reference in New Issue