Re: How do you write tests if you aren't sure what the result should be?
Michal Svoboda <[email protected]>
| Newsgroups | gmane.comp.programming.test-driven-development |
|---|---|
| Message-ID | <[email protected]> |
JeffGrigg wrote:
> For a pragmatic answer: Write the code. Run it. Observe the result.
> Validate that the result is "reasonable." [...whatever the heck THAT
> means!!!] Put the result in your test as an assertion.
>
> Then you'll at least know when something changes.
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
------------------------------------
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/