Assumptions: We use .NET coding against SQL Server 2005
I'm just thinking Was that how most people were involved in affecting their database in the unit test? I know when and where to use the joke, but when you want to move it past and actually do some database tests ... What strategy are you using to setup your database? Do you do the test? Or set up a certain scenario in the database and run many tests against that "world situation" any advice will help.
I run a testcase against an empty database, which means that only the database schema exists, But no data is examined, actual data is tested and removed as required by trial cases or setup and TeDown takes more time than preparing a prepared database, but the database is more resistant against schema changes.
Comments
Post a Comment