Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15024 > unrolled thread

Re: How to compile hashlib.c for testing?

Started byChet Ramey <chet.ramey@case.edu>
First post2018-12-31 14:41 -0500
Last post2018-12-31 14:41 -0500
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#15024 — Re: How to compile hashlib.c for testing?

FromChet Ramey <chet.ramey@case.edu>
Date2018-12-31 14:41 -0500
SubjectRe: How to compile hashlib.c for testing?
Message-ID<mailman.6640.1546285292.1284.bug-bash@gnu.org>
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/

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web