Is it wrong to favour integration testing over unit testing?
===

We're running a project on which we started adopting test-driven design long after the development was started.

We have both unit tests and integration tests. Integration tests are run on a real database, initialized in a known state before the tests are run.

As we write tests, we start noticing than even for classes that could be tested in the "standard way", in isolation & with mock objects, it has actually become faster, and cleaner (read: shorter & easier to understand code) to just use real objects/services directly talking to the database, rather than cluttering the test class with complicated mock objects setup.

Is there anything wrong with this approach?