Re: Test first as specification
- From: "Nick Malik [Microsoft]" <nickmalik@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Jul 2005 09:01:13 -0700
Hello Phlip,
> Your situation divides authority from responsibility. The specifying team
> doesn't have the responsibility to prove the designs. The remote team
> doesn't have the authority to improve the specifications. (And when tests
> drive development, writing tests in isolation is just like drawing models
> in
> isolation, and ordering someone else to implement the design.)
Excellent point. This is exactly why I asked on this forum. Thank you.
>
> To close this loop, the local team should implement at least 3 client
> applications for this framework.
Problem is that we are creating a small framework from scratch. To
implement a valid "application as a test" approach, the framework would have
to already exist. This is why I was discussing unit tests as specification,
not validation.
Once the framework is done, many apps will be based on it and I'm sure that
defects will be found.
Can we close the loop in another way? By emphasizing that unit tests can be
changed by the implementing team?
>
> And send a TDD coach to the remote team, to get them over the learning
> curve
> and show them out easy pure TDD is.
That isn't going to happen. Let's look for alternatives.
>
> Then share the responsibilities on both sides. Each team writes tests and
> code.
That's the core of the advice I'm taking away. Any followup to my comments?
--
--- Nick Malik [Microsoft]
MCSD, CFPS, Certified Scrummaster
http://blogs.msdn.com/nickmalik
Disclaimer: Opinions expressed in this forum are my own, and not
representative of my employer.
I do not answer questions on behalf of my employer. I'm just a
programmer helping programmers.
--
.
- References:
- Test first as specification
- From: Nick Malik [Microsoft]
- Re: Test first as specification
- From: Phlip
- Test first as specification
- Prev by Date: Re: OO Design induces an existential crisis
- 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
|