> The database should be part of the tests. Do not stub it. I've never seen this work well. The tests either rely on a shared/remote database or on a local da

> The database should be part of the tests. Do not stub it. I've never seen this work well. The tests either rely on a shared/remote database or on a local database instance that has to be set up/torn down between tests. Both approaches cause unending headaches in terms of false positives, onboarding new developers, dependency problems and maintenance.