Re: Test first as specification
- From: ggroups@xxxxxxxxxxx
- Date: 8 Aug 2005 04:13:23 -0700
Lurker wrote:
> "Robert C. Martin" <unclebob@xxxxxxxxxxxxxxxx> wrote in message
> news:akkcf1d223tg2v6983f4nsmigirblqrht5@xxxxxxxxxx
>> I completely disagree. Specifications are highly detailed declarative
>> statements that do not include intent. Intent is always commentary.
> Let me see if I got it right. Acording to you, specifications
> do not include intent? So what are they for then? I mean,
> the whole point of the specs is to communicate the intent,
> isn't it?
This is for Lurker, and also for Daniel Parker and Dmitry Kazakov :
We have SPEC, which is a specification of something for which an
implementation IMPL is required. We have TEST, which is a set of
tests that attempt to show that IMPL conforms to SPEC.
The premise is that there is a function f such that :
1. f(SPEC) = TEST
Succinctly, f allows the derivation of a set of tests from a spec.
2. Now what we continually hear from the XP/TDD is :
The tests are the specification.
3. From 1, 2 implies (SPEC = TEST)
4. Lurker IMHO is asking the following question :
Given f-inverse(T) = S, SPEC = some programming language,
show us the elements of TEST such that we can determine whether
f-inverse(TEST) = SPEC.
Given that a programming language may be too complex for debate,
what example would someone suggest ??
Late last yr I proposed the game of Go, where I would write SPEC
(using mathematical techniques) for the game, and an XP bod would write
TEST as "customer" tests. The premise being that what was specified/
omitted/incorrect using either approach could be scrutinised. That one
soon went quiet.
Shall we be topical, and chose something like Depth First Search of
directed graphs ??
Something else ?? I (and no doubt others) will be open to offers.
Regards,
Steven Perryman
PS: I have more interest than others in SPEC and f, because it is
the basis of the specification-directed testing method. Similarly for
f-inverse (Design for Testability) , because it leads to the creation
of output-independent test infrastructure.
.
- Follow-Ups:
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- References:
- Re: Test first as specification
- From: Roger L. Cauvin
- Re: Test first as specification
- From: paul campbell
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- From: Daniel Parker
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- From: Daniel Parker
- Re: Test first as specification
- From: Laurent Bossavit
- Re: Test first as specification
- From: Daniel Parker
- Re: Test first as specification
- From: Robert C . Martin
- Re: Test first as specification
- From: paul campbell
- Re: Test first as specification
- From: Robert C . Martin
- Re: Test first as specification
- From: Lurker
- Re: Test first as specification
- Prev by Date: Re: Singleton Pattern
- Next by Date: Re: OOP/OOD Philosophy
- Previous by thread: Re: Test first as specification
- Next by thread: Re: Test first as specification
- Index(es):
Relevant Pages
|