bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: How to run bash test suite


From: Chet Ramey
Subject: Re: How to run bash test suite
Date: Sun, 2 Jul 2017 12:46:05 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1

On 7/2/17 3:30 AM, Phi Debian wrote:

> I grabed the latest source code available with my ubunto distro and
> made a bash build. All is fine. I'd like to run the test suite, and I
> found no docco about it. Did a brute "make test" from the build src
> dir, but I don't understand how to decipher all the output there,
> should I trust it and place it in a reference output before doing
> shell hacks experiments and rerun and compare outputs ? Or does the
> test self sufficient, i.e produce errors in its outputs ? I can see
> warning: may be errors will shows up as error: and then a simple make
> test >out 2>&1 is enough then grep error: out

`make tests' (or `test' or `check') from the build directory runs the
bash test suite.  The first thing it displays is intended to explain the
output:

"Any output from any test, unless otherwise noted, indicates a possible
anomaly"

The only output should be the name of the test (e.g., run-exp) and any
warnings that test displays about the expected output, e.g.

"warning: the text of a system error message may vary between systems and
warning: produce diff output."

If you get diff output (lines prefixed by `<' or `>') and there isn't a
warning associated with the test telling you it's expected, that's a
problem.

Chet
-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/



reply via email to

[Prev in Thread] Current Thread [Next in Thread]