Re: How do you write tests if you aren't sure what the result should be?

On Sun, Mar 24, 2013 at 11:40 AM, Michal Svoboda <[email protected]> wrote:

> **
>
> I think thats not such a bad approach. We use it quite a lot:
>
> 1. write dirty code of what you "want to do" (aka "spike")
> 2. observe the result
> 3. write automatic tests on anything that you verified manually
> 4. refactor/test-drive "mercilessly" and write new tests as you go
>
> I think that the term for this is "Characteristic Tests", I was
first introduced to it in Michael Feathers Work.
but I'm not sure if it has a special section is his "Working with Legacy
system": book or was it in a later video session i saw.
A very useful technique in general, and should be an excellent idea in this
case.

Lior

>  _
>


[Non-text portions of this message have been removed]



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

Yahoo! Groups Links

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

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/testdrivendevelopment/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/