Module

Test

There's no documentation for this item.

Modules
Unit Unit testing is making waves all over the place, largely due to the fact that it is a core practice of XP. While XP is great, unit testing has been around for a long time and has always been a good idea. One of the keys to good unit testing, though, is not just writing tests, but having tests. What’s the difference? Well, if you just write a test and throw it away, you have no guarantee that something won’t change later which breaks your code. If, on the other hand, you have tests (obviously you have to write them first), and run them as often as possible, you slowly build up a wall of things that cannot break without you immediately knowing about it. This is when unit testing hits its peak usefulness.
Public Attributes
base
collector
exclude
filters
output_level
pattern
runner
suite
to_run
workdir
Public Methods
keyword_display
new
options
process_args
run
Comments

Have your say
Please use Textile formatting (click here for a cheat sheet). Use <code/> and <pre/> for code samples.
Click here to login with OpenID to to post comments.