[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-wget] Wget tests
From: |
Tim Rühsen |
Subject: |
Re: [Bug-wget] Wget tests |
Date: |
Mon, 15 Aug 2016 22:03:43 +0200 |
User-agent: |
KMail/5.2.3 (Linux/4.6.0-1-amd64; KDE/5.23.0; x86_64; ; ) |
On Montag, 15. August 2016 15:06:52 CEST Dale R. Worley wrote:
> Can someone give me a hint how the wget tests work? The test
> directories seem to contain no high-level documentation. As far as I
> can tell, the pairs of files *.{trs,log} either are or correspond to the
> various tests, but I can't find the file(s) that specify what the test
> invocations of wget are, nor what files the test HTTP server sees.
We use standard automake tests (search the internet if you are interested in
details).
We have the 'legacy' tests/ directory with tests written in Perl. And the
'current' testenv/ directory with tests written in Python.
See tests/Makefile.am resp. testenv/Makefile.am for the list of executed tests.
The output of each test executed by 'make check' is saved in a .log file.
You can execute a single test with e.g.
$ cd tests
$ make check TESTS=Test--start-pos
(creates a .log file)
or with e.g.
$ cd tests
$ ./Test--start-pos.px
(prints output on screen, creates no .log file)
Regards, Tim
signature.asc
Description: This is a digitally signed message part.