From: Mike Gran <spk121@yahoo.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Guile Devel" <guile-devel@gnu.org>
Subject: Re: On white-box tests
Date: Wed, 19 Aug 2009 05:14:12 -0700 [thread overview]
Message-ID: <1250684052.18373.858.camel@localhost.localdomain> (raw)
In-Reply-To: <87d46sci6o.fsf@gnu.org>
On Wed, 2009-08-19 at 10:38 +0200, Ludovic Courtès wrote:
> Hello!
>
> Just a note that I've been meaning to send for some time.
>
> "Michael Gran" <spk121@yahoo.com> writes:
>
> > http://git.savannah.gnu.org/cgit/guile.git/commit/?id=9b0c25f6d18d5be318ea3a47fd87cf7e63b689e1
>
> [...]
>
> I'm not fully convinced by some of these "string internals" tests,
> though. These are "white box tests". I believe these tests are mostly
> useful when written by someone different than the one who implemented
> the code under test, both of whom following a given specification. When
> someone writes both the code and the white box tests, I'm afraid they
> end up writing the same code twice, just differently. For example:
I know what your saying. I was just a kid with a new toy.
In my line of work, where 100% code coverage of test suites is a common
requirement, we end up writing many such overly obvious tests. They are
often the only way to hit some internal branches. They are often
pointless.
> What do you think?
Keep it or dump it. It's all good.
>
> Thanks,
> Ludo'.
Thanks,
Mike
next prev parent reply other threads:[~2009-08-19 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Majpl-0008Ga-T9@cvs.savannah.gnu.org>
2009-08-19 8:38 ` On white-box tests Ludovic Courtès
2009-08-19 12:14 ` Mike Gran [this message]
2009-08-19 13:53 ` Ludovic Courtès
2009-08-19 14:28 ` Mike Gran
2009-08-19 14:41 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1250684052.18373.858.camel@localhost.localdomain \
--to=spk121@yahoo.com \
--cc=guile-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).