Re: How to compile hashlib.c for testing?

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: How to compile hashlib.c for testing?
Date	2018-12-31 14:41 -0500
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.6640.1546285292.1284.bug-bash@gnu.org> (permalink)
References	<CABrM6wm+x0hGuSVYeRLSE9=6vuadxP++4+gSoG+Tm7_yYN4Duw@mail.gmail.com> <31ae9367-7968-aff5-d0e8-0f9da667d584@case.edu> <CABrM6w=a7NyF8xBkooeJojkAK_b=_rz9VsnWt2MWV3HN4BA9Eg@mail.gmail.com> <2d74e9ca-ae78-4661-ec86-36645ffa8047@case.edu> <CABrM6wnPudDS9Z49LW8cF4V_40sRMqRTNdVwcW7QhsKGv38Q7Q@mail.gmail.com>

Show all headers | View raw

On 12/29/18 5:44 PM, Peng Yu wrote:
>> That code hasn't really changed in almost twenty years. All the testing
>> was done long ago.
> 
> Do you keep all the testing code in the bash repository? 

Yes. The test suite exists in the tests subdirectory.

> Given the fugal
> testing code that is in the bash source, it is doesn't seem that the
> current testing code can cover all the branches of the source code. 

(That's not a word.)

The current testing code, the last time I ran the test suite through
gcov, gives pretty good coverage of the non-interactive features. For
instance, it covers about 86% of subst.c, which is the word expansion
code, among other things.

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

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread

Thread

Re: How to compile hashlib.c for testing? Chet Ramey <chet.ramey@case.edu> - 2018-12-31 14:41 -0500

csiph-web