June 21, 2005 at 4:40 am
Hi there
In the past we have developed some SQL functionality. One problem we have is to efficiently test the SPs.
If we create test scenarios for testing a little piece of code insight a SP (-> white box testing), we cannot guarantee that we have no unwanted side effects, but the tests are very efficient for this piece of code even if the base structures of the database changes. If we test with the full productive load (of course in a testing environment) we have better tests to detect side effects but if the base structure changes we have a lot to do to adapt all the test SPs...
What do you think? Are there really good tools (which are also payable) to manage the tests with large tables or would you prefer the testing with the small units?
Roger
June 22, 2005 at 7:47 am
Swing over to SourceForge.net and search for SqlUnit. It uses the nUnit test driven development approach for TSQL. It would allow for a set up step, an execution step, verification of the output of the exection and a cleanup step. Some of our developers have put it to use. That's the closest I'm aware of to what you're asking for.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply