On 1/30/06, Bruce D'Arcus [EMAIL PROTECTED] wrote:
I still need to wrap my head around this (particularly exactly what
kinds of methods to create tests for), but I guess the idea is to
create a file full of this sort of stuff?
Yep, write tests for the code that doesn't exist and run them and
You typically want to test how a user will want to use your library.
You don't want to write tests for internal stuff. If there are a
sequence of interpendent events that need to be tested I tend to
bundle them in an individual test method.
Testing does take time. When you first start writing
