Grant Fritchey (10/28/2008)
While I do agree, we use Visual Studio Team System Database Edition for unit testing now, a few of your negatives probably shouldn't be on the list. #4 especially. You shouldn't be running unit tests against production machines, ever. Unit testing is a development only process that should be isolated from other systems, especially a production system.
I guess I wasn't clear about what I meant for #4.
We wanted to use TSQLUnit for data validation as well as unit testing.
For example: let's say we run some data export for a client.
We are creating a file (xml, csv, flat file) to send to them.
After we create the file, we load it into the database.
We then want to run SQL scripts against the file comparing the file to the original data in order to validate the file.
We would have to do this in our Production environment.
Also, when we were using TSQLUnit, we only ever created a test database by deploying code there first. You can keep it seperate from your development, integration & QA databases. It's an extra step in development though.
That sounds like it would take a lot of extra time, and when does development ever have extra time?!?