[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How to compile hashlib.c for testing?
From: |
Chet Ramey |
Subject: |
Re: How to compile hashlib.c for testing? |
Date: |
Mon, 31 Dec 2018 14:41:19 -0500 |
User-agent: |
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 |
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/