<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://sqlblog.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Benefit from Unit Testing T-SQL: Speed up Your Test Harness</title><link>http://sqlblog.com/blogs/alexander_kuznetsov/archive/2010/10/15/benefit-from-unit-testing-t-sql-speed-up-your-test-harness.aspx</link><description>Ideally unit test harness should run very fast. Because all unit testing involving a database is quite slowish, we need to apply some effort to ensure that our tests finish in acceptable time. This slowness might not be a concern when we try out a cool</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP2 (Build: 61129.1)</generator></channel></rss>