blocks|key|4764590|text|您可以将所有内容包装在一个事务中，最后只需回滚所有内容。我就是这么做的。它还允许并行运行测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4764591|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You could wrap everything in a transaction and in the end just rollback everything. That's how I do it. It allows also to run tests in parallel.

blocks|key|1086028|text|使用SQL+Server+Compact如何，使用nhibernate+schema从映射文件创建数据库，并为每个测试加载数据。如果你谈论的是微不足道的数据量。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1086029|看看这篇博文-+Using+SQL+Server+Compact+Edition+for+Unit+testing|offset|length|1086030|或者，您可以使用Fluent+Migrator创建数据库模式并加载每个测试的数据。|1086031|entityMap|0|LINK|mutability|MUTABLE|url|http://www.differentpla.net/content/2009/03/using-sql-server-compact-edition-unit-testing^0|0|8|1D|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@$D|R|E|S|1|T]]|A|$]]|$1|F|3|G|5|6|7|U|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

what about using SQL Server Compact, create the database from the mapping files using nhibernate schema create and load the data for each test. if you are talking about a trivial amount data.

Have a look at this blog post - <a href="http://www.differentpla.net/content/2009/03/using-sql-server-compact-edition-unit-testing" rel="nofollow">Using SQL Server Compact Edition for Unit testing</a>

Alternativly you could use Fluent Migrator to create the database schema and load the data for each test.

blocks|key|1086055|text|为什么要在测试中使用DB呢？你当然应该嘲笑持久化机制？除非您真的在尝试测试这部分功能，否则您实际上是在浪费时间和资源来插入/更新/删除数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1086056|您的测试依赖于ms+sql细节和返回的数据这一事实暗示了您的体系结构需要查看的可能性。|1086057|我并不想在这里听起来很粗鲁--我只是很惊讶没有其他人在这件事上跟你搭讪。|1086058|w://|1086059|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

Why are you even using a DB in your tests? Surely you should be mocking the persistence mechanism? Unless you're actually trying to test that part of the functionality you're wasting time and resources actually inserting/updating/deleting data. 

The fact that your tests rely on ms sql specifics and returned data hints at the possibility that your architecture needs looking at.

I'm not meaning to sound rude here - I'm just surprised no one else has picked you up on this.

w://

blocks|key|1092153|text|在过去，我做了几件事来帮助加速数据库集成测试。我做的第一件事是，我最终拥有了一个sql脚本，它实际上是从头开始创建整个数据库。这可以使用Red-Gate+SQL+Compare之类的工具轻松地与空白数据库进行比较。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1092154|其次，我创建了一个脚本，用于从现有数据库中删除所有数据库对象。|1092155|然后，我需要一个用测试数据填充数据库的脚本。同样，使用Red-Gate工具创建起来也很简单。你不需要/想要大量的数据，只要足够覆盖你的测试用例即可。|1092156|准备好这些项目后，我创建了一个测试类，其中包含我所有的只读操作。在该类的init中，我清除了一个本地sql+server+express实例，运行了创建脚本，然后运行了填充脚本。这确保了为所有只读测试正确初始化数据库。|1092157|对于实际操作数据库的测试，我们只是做了与上面相同的路由，只是我们在test+init上做了，而不是在类init上。|1092158|显然，数据库操作测试越多，运行所有测试所需的时间就越长。如果它变得难以控制，您应该考虑对测试进行分类，只在本地运行必要的测试，并在持续集成服务器上运行完整的套件。|1092159|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

There are a couple of things that I've done in the past to help speed up database integration tests. First thing I did was I ended up having a sql script that actually creates the entire database from scratch. This can be easily accomplished using a tool like Red-Gate SQL Compare against a blank database.

Second I created a script that removed all of the database objects from an existing database.

Then I needed a script that populated the database with test data. Again, simple to create using Red-Gate tools. You don't need/want a ton of data here, just enough to cover your test cases.

With those items in place, I created one test class with all of my read-only operations in there. In the init of that class, i cleared a local sql server express instance, ran the create script and then ran the populate script. This ensured the database was initialized correctly for all of the read-only tests.

For tests that actually manipulate the database, we just did the same routing as above except that we did it on test init as opposed to class init.

Obviously the more database manipulation tests you have, the longer it will take to run all of your tests. If it becomes unruly, you should look at categorizing your tests and only running what is necessary locally and running the full suite on a continuous integration server.

We have a rather extensive test suite that takes forever to execute.
After each test has completed, the database (MSSQL) needs to be emptied so it is fresh for the next testcase.
The way we do this is by temporarily removing all foreign keys, TRUNCATE'ing all tables, and re-adding the FKs.

This step takes somewhere between 2-3 seconds, according to NHProfiler. All the time is seemingly spent with the FK operations.

Our current method is clearly not optimal, but which way should we go to improve the performance ? The number of elements which are actually deleted from the DB is completely insignificant compared to the number of operations for the FK removal/additions.

Using an in-memory SQLite database is not an option, as the code under test uses MSSQL specific operations.

Nhibernate Nunit - clear database between testcases

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我们有一个相当广泛的测试套件，需要永远执行。每次测试完成后，数据库(MSSQL)都需要清空，以便为下一个测试用例刷新。我们做到这一点的方法是临时删除所有外键，截断所有表，然后重新添加FK。根据NHProfiler的说法，这一步需要2-3秒。所有的时间似乎都花在了FK操作上。我们目前的方法显然不是最优的，但是我们应该走哪条路来提高性能呢？与FK移除/添加的操作数量相比，从数据库中实际删除的元素数量完

问Nhibernate Nunit -测试用例之间的清除数据库
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Nhibernate Nunit -测试用例之间的清除数据库EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Nhibernate Nunit -测试用例之间的清除数据库
EN