Then again writing tests can be just as unproductive as writing getters and setters. Maybe that is one reason that it has become so popular (makes you feel more productive)?
I think the hope is you write one test then write the code to make it pass. In theory the code and tests grow at a similar rate. If one treats the two activities as separate then i think it would be very easy to get caught up in the productive feeling that writing tests gives without receiving a good portion of the benefits.