So to sumerize,
1. Research the problem to work around unknowable areas.
1a. Become convinced that its possible to know the unknowable in an
abstract way.
2. Abstract the things which cause the problem to be unknowable and create
mocks for them.
3. Massage the known solution to be broken up into testable units.
4. Profit.
Is that correct?
On Feb 18, 2013 7:01 AM, "Amir Kolsky" <kolsky@...> wrote:
**
Sorry for not being clear.
I meant that the derivation of the formulae that you THEN implemented in
TDD
did not have anything to do with TDD.
From: testdrivendevelopment@...
[mailto:testdrivendevelopment@...] On Behalf Of Ron Jeffries
Sent: Sunday, February 17, 2013 2:41 PM
To: testdrivendevelopment@...
Subject: Re: [TDD] How do you write tests if you aren't sure what the
result
should be?
Hi Amir,
On Feb 17, 2013, at 11:52 AM, "Amir Kolsky" kolsky@...
wrote:
Thing is, none of it had anything to do with TDD...
Let me suggest that you read again, and think again ...
Ron Jeffries
www.XProgramming.com
You never know what is enough unless you know what is more than enough. --
William Blake
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
