Re: [Subtext-devs] new devs guide: unit tests

[Phil H. <ha...@gm...>]

In general, your unit tests should be small and compact. They test a *unit*
of code.  Also, unit tests don't guarantee correct execution, they give you
a degree of confidence.

 

So while your unit test could have a bug, it's fairly unlikely that your
test is wrong in such a way that the test passes, when it shouldn't.  To
prevent that from happening, we follow the Red-Green factor approach.

 

For example, suppose you are fixing a bug.  You write a test that should
pass, but doesn't because of the bug.  Run the test and make sure it fails.
If it doesn't, you've done something wrong.  Then you fix the bug. Now your
test should pass.   If it doesn't, you've done something wrong.

 

Phil

 

From: sub...@li...
[mailto:sub...@li...] On Behalf Of David Frank
Sent: Tuesday, November 14, 2006 2:49 PM
To: sub...@li...
Subject: [Subtext-devs] new devs guide: unit tests

 

how about talking briefly in the wiki guide about unit tests, link to those
links you sent me on what they are and why they're good, and even how to
launch the mbunit proggie, as I too was unaware of that.  

 

I've looked at some of the existing tests and they makes sense - trying
variations of input and testing to see if you get the expected output for
the various routines contained therein....

 

but my question is, how do you know that you're being comprehensive enough
with what you're testing with?  though, I suppose some test is better than
no test...  

 

is it possible for your test to have a problem and need a test of its own?
:)