Database Unit Testing
November 22nd, 2002
One of the main problems I've encountered some times now, is: how can I unit test programs that make use of a DB? The testing is very likely to read (duh!) and change the data in the DB, thus making the tests dependent on (a) the scrap tests that you do manually while coding, and (b) each other.
Of course, we have dbUnit (with its academic/philosophical base), but this approach requires 4 (four!) databases. In the company I work in now, it appears to be unfeasible to have one database (which happens to be Oracle here) per developer. So now I'm looking for the silver bullet.
I already encountered one interesting read, but it seems to be a discussion without a real conclusion.
(Remember you can always send me your thoughts.)
Of course, we have dbUnit (with its academic/philosophical base), but this approach requires 4 (four!) databases. In the company I work in now, it appears to be unfeasible to have one database (which happens to be Oracle here) per developer. So now I'm looking for the silver bullet.
I already encountered one interesting read, but it seems to be a discussion without a real conclusion.
(Remember you can always send me your thoughts.)
Leave a Reply