I wonder if the people who proclaim unit tests shouldn't hit the database have SSD's.
Claes Wallin (韋嘉誠) shared this.
Show all 9 replies
I rather like doing very course tests to drive development, and then create unit tests as a form of debugging. You are excercising the code to find out what happened, so why not make that excercise permanent and versioned. And then your test suite grows organically on demand.
So, I absolutely think "unit tests" should not hit the db. But then i also don't think unit tests are all we should be doing, or maybe not even the first thing we should be doing.
As you say, the most important thing is to get people to do any testing at all.
So, I absolutely think "unit tests" should not hit the db. But then i also don't think unit tests are all we should be doing, or maybe not even the first thing we should be doing.
As you say, the most important thing is to get people to do any testing at all.
Claes Wallin (韋嘉誠) at 2015-08-11T13:20:18Z
Amitai Schleier likes this.
The book "Working Effectively With Legacy Code" is about the same theme as "Test-driven repair", and methods for introducing testing to code that wasn't written with it in mind, in incremental, minimally-invasive steps. I've looked through it quickly, and it's on my long to-read-list. Lots of people recommend it. Sort of C++-specific, though.