How to run bash test suite

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

How to run bash test suite

Phi Debian
Hi All,
I tried to subscribe to bug-bash but never got the confirmation mail.

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

Any help appreciated.
Cheers,
Phi

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to run bash test suite

Chet Ramey
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    [hidden email]    http://cnswww.cns.cwru.edu/~chet/

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to run bash test suite

Phi Debian
Hi Chet,
Thanx for the primer on QA :)

I did manage to run them.
I reworked run-all to run all this in parallel, I fixed some to ad
more determinism in the output (background jobs), I got now a fast way
to run the QA and that trig attention flag only when needed.

Let's hack the bash now :)

Cheers,
Phi

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to run bash test suite

Chet Ramey
On 7/3/17 9:34 AM, Phi Debian wrote:
> Hi Chet,
> Thanx for the primer on QA :)
>
> I did manage to run them.
> I reworked run-all to run all this in parallel, I fixed some to ad
> more determinism in the output (background jobs), I got now a fast way
> to run the QA and that trig attention flag only when needed.

Send your changes and I'll take a look at them.

Chet


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

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: How to run bash test suite

Bob Proulx
In reply to this post by Phi Debian
Phi Debian wrote:
> I tried to subscribe to bug-bash but never got the confirmation mail.

You must have successfully received and replied to the confirmation
email because I looked at the subscriber list and you are subscribed.
Obviously not needed now but if you have trouble with the mailing
lists write to the mailing list owner at [hidden email] to
contact the humans who help with the mailing list.  This is the email
address convention for all of the Mailman managed mailing lists.

Bob

Loading...