Well, without adding dbfit to the mix, I'll propose keeping it simple.
First you run nearly all of your tests up to, but no further, the db abstraction layer (you do have one right?). Then to test the abstraction layer, really use the database - but set up a transaction for each test, and roll it back at the end.
John D.
> -----Original Message-----
> From:
testdrivendevelopment@...
> [mailto:
testdrivendevelopment@...] On Behalf Of fsharpmike
> Sent: Monday, March 10, 2008 8:44 PM
> To:
testdrivendevelopment@...
> Subject: Re: [TDD] How to TDD a Reporting Application?
>
> Hi,
>
> I appreciate the responses. What I'm really having trouble with
> is testing the database. Specifically, setting up the test data. For
> the first time ever I'm considering mocking test data, which I've
> always been loathe to do, but this data is so complex, and I'm only
> reading it, so it might not make sense to do actual database inserts
> in this case. Thoughts?
>
> Thanks,
> Mike
>
>
>
>
> Yahoo! Groups Links
>
>
>
