For actual unit testing, you can't go past Roy Osherove's The Art Of Unit Testing as ysolik mentioned. It goes through the actual technology used. Things like what is a mock, fake, stub, frameworks to use, test naming etc.
Other books such as Kent Becks Test Driven Development, which Matt suggested go through TDD, which is one way of doing unit testing, but it doesn't go into as much depth about unit testing as a technology. This book goes through an example application and goes through what would go through your head when writing tests first and the code afterwards.
A free article that is similar to Kent Becks book, in that it tells the story of developping an application, tests first is the XP Episode bowling example, by Robert Martin and Robert Koss.
I've read both books, starting with The Art of Unit Testing, and then moved onto Kent Becks to get a good idea of the process. I think that's a good way of learning it, if indeed you do want to learn Test Driven Development.