programmer, object tests

In one of the sample chapters, JB explains his terminology of progammer and object tests. I assume that programmer tests include object tests and integration/functional tests written by the programmer.

Do you use any distinction between object tests that run as pure unit tests and those that require a database, server, etc?

Originally posted by Jeanne Boyarsky:
those that require a database, server, etc?

Isn't this by definition an functional/integration test?

Lasse,
Yes, of course. I am trying to figure out if JB includes those as object tests in his terminology. Sometimes they test just one object (like a DAO.)

I use the term "isolated object test" to refer to a test that exercises a single object in isolation. That means that I simulate all other collaborators, be they databases, network resources, or other Java objects.

A "programmer test" is any test a programmer writes to increase her confidence that the code does what she thinks it does.

J.B.,
That was the terminology I was looking for! What do you call the non-isolated object tests?

An object test that isn't isolated is, I suppose, an integration test; but for me, object tests should be isolated to the extent possible. I emphasize this point by throwing in the (redundant) word "isolated".

J. B.,
Ok. I understand the terminology now. Thanks!