> Mocking is faster and often feels more straightforward. This makes it a unit test. > However, testing against a real database uncovers hidden pitfalls that

> Mocking is faster and often feels more straightforward. This makes it a unit test. > However, testing against a real database uncovers hidden pitfalls that can appear as the application matures. This makes real-database testing not a unit test. Maybe it's integration testing. So basically the author is against unit tests (or isn't quite sure of the difference from integration testing)