I have teh first cut of the tsqlUnit running in the Assembly.

It can compare table and procedure stuctures, which now gives us the capability of defining strucutres for certain returns and confirming that the Stored Procs meet those structures.

Additionally I have the mock framework running so that we can define mock tables ... next is to build mock record/result sets and such to perform actions on ....

So things are starting to come together ... next item is to finish the Mocking framework and then to move the primary logic into the Assembly so that I can handle all the error trapping and transactions there enabling much easier flow logic.

Will have to do some more reading on the SQL Server RaiseError functionality and make things go from there.

All in all it is starting to come together, which is good as I have another compnay interested in making use of it ...

Went out to dinner on friday night with the Managing Director of Release Management for the NYSE and we shared ideas and such on some technology ... he was intrigued at the idea of unit Testing the db and wants to have a look at the product once I move the logic into the Assembly.

OK, I now have a C# assembly that has a method called tableCompare that takes a stored Proc name and a table name as parameters and it then connects to the database and gets gets the structure of the table and calls the stored proc and captures the structure of the return ...

Current they just print out to the SQL message window, next is to start the comparison system ... I am stoked at this ... and the techniques are not that hard to do once you get used to it.