Re: TDD for numerical algorithms

Adam, et al,

Adam Sroka wrote:
> BTW, testing intermediate state in order to drive a particular
> implementation is not TDD. TDD is concerned with the behavior of the
> objects in your system. Could I write a test that says, "line 6 of the
> program shall say ..."? Sure I could, and it would compel a particular
> implementation, but it would not even resemble TDD.

I find that test-driving a particular algorithm is sometimes useful. 
I'll agree that it doesn't feel the same as TDD, though.  At the Floyd 
Code Retreat, Corey Haines called this a form of Test First Development, 
distinct from TDD.  I think I like that distinction.

  - George

-- 
  ----------------------------------------------------------------------
   * George Dinwiddie *                      http://blog.gdinwiddie.com
   Software Development                    http://www.idiacomputing.com
   Consultant and Coach                    http://www.agilemaryland.org
  ----------------------------------------------------------------------



------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/refactoring/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/refactoring/join
    (Yahoo! ID required)

<*> To change settings via email:
    [email protected] 
    [email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/