blocks|key|1349651|text|Team+System可能是最知名的解决方案，但您也可以尝试TSQLUnit+(SourceForge)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1349652|我自己还没有用过它，但this+article在引入它方面做得很好。|1349653|entityMap|0|LINK|mutability|MUTABLE|url|http://sourceforge.net/apps/trac/tsqlunit/|1|http://www.sqlservercentral.com/articles/TSQLUnit/64357/^0|U|8|0|0|B|C|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$A|U|B|V|1|W]]|C|$]]|$1|F|3|-4|5|6|7|X|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]]]

Team System is probably the best-known solution, but you could also try <a href="http://sourceforge.net/apps/trac/tsqlunit/" rel="nofollow noreferrer">TSQLUnit</a> (SourceForge).

I haven't used it myself, but <a href="http://www.sqlservercentral.com/articles/TSQLUnit/64357/" rel="nofollow noreferrer">this article</a> does a decent job of introducing it.

blocks|key|3810252|text|查看http://www.sqlservercentral.com/articles/Testing/66553/和http://www.sqlservercentral.com/articles/Database%2BDesign/66845/|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3810253|这是一篇关于在T-SQL中做所有事情的相当粗糙的文章。|3810254|你有没有想过仅仅为了测试而使用NHibernate和TestDriven或类似的东西？|3810255|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sqlservercentral.com/articles/Testing/66553/|1|http://www.sqlservercentral.com/articles/Database%2BDesign/66845/^0|2|1J|0|1M|1R|1|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]|$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|C|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]|P|$5|K|L|M|C|$N|Q]]]]

Checkout <a href="http://www.sqlservercentral.com/articles/Testing/66553/" rel="nofollow noreferrer">http://www.sqlservercentral.com/articles/Testing/66553/</a>
and <a href="http://www.sqlservercentral.com/articles/Database+Design/66845/" rel="nofollow noreferrer">http://www.sqlservercentral.com/articles/Database+Design/66845/</a>

This is a fairly crude article about doing everything within T-SQL.

Have you thought about using NHibernate and using TestDriven or similar just for the tests?

blocks|key|5278943|text|在我无法访问team+system+for+db+pro的项目中，我使用了结合了msbuild的sql脚本和msbuild的sdc任务库(http://www.codeplex.com/sdctasks)。msbuild脚本调用sdc任务，以特定的顺序运行我的sql脚本(例如，create+db、create+tables等)并且在特定的连接字符串上。脚本总是检查一个对象是否存在，并首先进行拆卸，然后重新构建它。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5278944|我放置在常规visual+studio数据库项目中的sql和msbuild脚本(它不做任何特殊操作，因此您可以选择使用一个简单的空项目)，因此一切都是受源代码管理的。|5278945|有了这样一组脚本，您就可以为每次测试运行设置一个新数据库。然后，您可以使用插入脚本用数据填充它，并对它运行单元测试。|5278946|这些脚本对于在不同环境中从头开始设置数据库也很有用(DEV/TST/QUA/...)|5278947|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeplex.com/sdctasks^0|1X|W|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|C|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|C|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]]]

On projects where I didn't have access to team system for db pro's, I have used sql scripts combined with msbuild and the sdc tasks library for msbuild (<a href="http://www.codeplex.com/sdctasks" rel="nofollow noreferrer">http://www.codeplex.com/sdctasks</a>). The msbuild script calls on an sdc task to run my sql scripts in a particular order (e.g. create db, create tables etc...) and on a particular connection string. The scripts always check if an object exists and do teardown first and build it back up.

The sql and msbuild scripts I place in a regular visual studio database project (which does nothing special, so you could choose to use a simple empty project), so everything is source-controlled.

with such a set of scripts , you can setup a new database for each test run. You can then use insert scripts to populate it with data and run unit tests against it.

These scripts are also useful for setting up databases from scratch in different environments (DEV/TST/QUA/...)

blocks|key|1343621|text|我能够充分地apply+a+test+driven+development+style+against+SQL+Server+databases+using+TSQLUnit。我遵循了与您描述的相同的流程，先编写一个失败的单元测试存储过程，然后进行必要的更改以使测试通过。随着时间的推移，我还建立了一套测试，在执行时验证了在进行任何新的更改时没有损坏。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1343622|有一些困难的地方(包括为现有的sprocs编写测试的极端困难)，但它特别适用于模式更改。但是，我建议使用T.S.T.+the+T-SQL+Test+Too1，它与TSQLUnit+(I+had+to+roll+my+own)不同，它内置了对断言的支持。|1343623|entityMap|0|LINK|mutability|MUTABLE|url|http://lexicalclosures.blogspot.com/2008/11/unit-testing-databases-with-tsqlunit.html|1|http://tst.codeplex.com/|2|http://lexicalclosures.blogspot.com/2009/02/its-true-and-not-false-how-to-assert.html^0|6|29|0|0|1G|Q|1|2J|K|2|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@$A|S|B|T|1|U]]|C|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]|$A|Z|B|10|1|11]]|C|$]]|$1|F|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]|N|$5|I|J|K|C|$L|O]]|P|$5|I|J|K|C|$L|Q]]]]

I was able to adequately <a href="http://lexicalclosures.blogspot.com/2008/11/unit-testing-databases-with-tsqlunit.html" rel="nofollow noreferrer">apply a test driven development style against SQL Server databases using TSQLUnit</a>. I followed the same flow as you described with writing a unit test sproc first that fails and then making the changes necessary for the test to pass. Over time, I also built up a suite of tests when executed validated that nothing broke while making any new changes.

There was some tough spots (including extreme difficulties in writing tests for existing sprocs) but it worked especially for schema changes. However, I would recommend looking at <a href="http://tst.codeplex.com/" rel="nofollow noreferrer">T.S.T. the T-SQL Test Too1</a> which unlike TSQLUnit (<a href="http://lexicalclosures.blogspot.com/2009/02/its-true-and-not-false-how-to-assert.html" rel="nofollow noreferrer">I had to roll my own</a>) has built-in support for assertions.

For several years I have been using a testing tool called qmTest that allows me to do test-driven database development for some Firebird databases. I write a test for a new feature (table, trigger, stored procedure, etc.) until it fails, then modify the database until the test passes. If necessary, I do more work on the test until it fails again, then modify the database until the test passes. Once the test for the feature is complete and passes 100% of the time, I save it in a suite of other tests for the database. Before moving on to another test or a deployment, I run all the tests as a suite to make sure nothing is broken. Tests can have dependencies on other tests, and the results are recorded and displayed in a browser.

Nothing new here, I am sure.

Our shop is aiming toward standardizing on MSSQLServer and I want to use the same procedure for developing our databases. Does anyone know of tools that allow or encourage this kind of development? I believe the Team System does, but we do not own that at this point, and probably will not for some time.

I am not opposed to scripting, but would welcome a more graphical environment.

Any suggestions?

Test-First development tool for SQL Server 2005?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

几年来，我一直在使用一个名为qmTest的测试工具，它允许我为一些Firebird数据库进行测试驱动的数据库开发。我为一个新特性(表、触发器、存储过程等)编写了一个测试。直到失败，然后修改数据库，直到测试通过。如果有必要，我在测试上做更多的工作，直到它再次失败，然后修改数据库，直到测试通过。一旦该特性的测试完成并100...

问SQL Server 2005的第一个测试开发工具？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问SQL Server 2005的第一个测试开发工具？EN