Re: How to compile hashlib.c for testing?

From	Peng Yu <pengyu.ut@gmail.com>
Newsgroups	gnu.bash.bug
Subject	Re: How to compile hashlib.c for testing?
Date	2018-12-29 16:44 -0600
Message-ID	<mailman.6532.1546123750.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>

Show all headers | View raw

> 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? Or you keep
the testing code separately from the bash source? 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. I
am wondering how to ensure the code contains as few bugs as possible
without full coverage testing cases? Thanks.

-- 
Regards,
Peng

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

Thread

Re: How to compile hashlib.c for testing? Peng Yu <pengyu.ut@gmail.com> - 2018-12-29 16:44 -0600

csiph-web