Re: [TFUI] Re: Is a bad test better than no test at all?

Tim Ottinger wrote:

> If the test runs quickly, returns true results (no tail chasing from false false negatives, no misdirection through false positives), then keep it.

False negatives are okay if they are instant. You could learn from
your most recent edit and capture the issue with a test closer to the
source. And/or you can Undo to get rid of the failure and try a
simpler change.

 It's useful. If it sometimes returns false results or takes a long
time, then fuzzy is bad.
>
>  Ultimately, I fall back on Michael Feathers' "1) runs quickly, 2) helps to isolate errors". If it is too fuzzy for either of the criteria, it's too fuzzy. Otherwise, not.

-- 
  Phlip
  http://c2.com/cgi/wiki?ZeekLand  <-- NOT a blog!!


 
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:
    mailto:[email protected] 
    mailto:[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/