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


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

Re: How to compile hashlib.c for testing?

Started byPeng Yu <pengyu.ut@gmail.com>
First post2018-12-29 16:44 -0600
Last post2018-12-29 16:44 -0600
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? Peng Yu <pengyu.ut@gmail.com> - 2018-12-29 16:44 -0600

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

FromPeng Yu <pengyu.ut@gmail.com>
Date2018-12-29 16:44 -0600
SubjectRe: How to compile hashlib.c for testing?
Message-ID<mailman.6532.1546123750.1284.bug-bash@gnu.org>
> 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

[toc] | [standalone]


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


csiph-web