4 ms·

Then just use a database for unit testing as well.

• globular-toast 2y ago
  Then you get a slow test suite. It's important to have a fast test suite to be able to do proper test driven development (which I still believe is the most efficient and effective way to write software, in general). Unit tests should be near 100% coverage. That means a lot of tests.
  • peterldowns 2y ago
    That's not always true — database-backed tests can be extremely fast, see https://github.com/peterldowns/pgtestdb https://github.com/peterldowns/pgtestdb.
  • bluGill 2y ago
    databases can run hundreds of test in a ms. Sure without you could get to thousands in that ms - who cares.
• astine 2y ago
  Because then you wouldn't be doing unit testing; you'd be doing integration testing. You'd also probably not be testing the database in a realistic configuration and thereby missing the whole point.