Comments on: When You Absolutely Need To Use A Real Database In Tests

By: Mike Scott

Mike Scott — Thu, 27 Aug 2009 20:00:49 +0000

I agree with Nik – the database should be tested fully in integration tests. To that end, I strongly recommend having a look at Fitnesse, at http://fitnesse.org.

By: Nik Radford

Nik Radford — Tue, 21 Jul 2009 15:45:09 +0000

Tests using real database = Intergration Tests
Tests not using real database = Unit tests.

You should do both. The first shows the code does as expected. The second shows code behaves as expected.

By: Craig Nicol

Craig Nicol — Tue, 21 Jul 2009 11:37:58 +0000

I’ve got two good reasons for doing this :

(1) I’ve worked on applications that rely on data and code in the db (which is horrible to work with in general.

(2) I’ve been burned with changes between collation and query syntax between the dev and live servers (make sure both run the same db version, and the same schema)

By: den Ben

den Ben — Mon, 20 Jul 2009 18:50:36 +0000

Common Sense ™

I actually kinda like the ‘insert some records and some other records and query for it’-approach.