Resharper 单元测试运行器明显慢于 NUnit 控制台
Resharper Unit Test Runner 的运行速度明显慢于 nunit-console 或 nunit gui。
例如，通过 nunit-console 进行 3800 个测试只需要 60 秒多一点的时间，但在 Resharper 单元测试运行器中运行这些相同的测试需要 5 分钟多的时间。为什么会有如此显着的差异？
由于我们的测试代码库已显着增长，这确实开始减慢我们的速度。还有其他人遇到过类似的问题吗？你是怎么处理的？
Resharper Visual Studio 集成非常好，但是我们可能需要求助于其他东西。
Resharper Unit Test Runner runs significantly slower than nunit-console or nunit gui.
For example, 3800 tests take just over 60 seconds via nunit-console, but those same tests take over 5 minutes to run in Resharper Unit Test runner. Why such a significant difference?
Since our test code base has grown significantly, this is really starting to slow us down. Has anyone else experienced similar problems? How have you dealt with it?
The Resharper Visual Studio integration is really nice, however we might need to resort to something else.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我遇到了同样的问题，然后我切换到 TestDriven.Net，它快如闪电。
I had the same issue and I switched to TestDriven.Net, it's lightning fast.
我不认为 Resharper 的目标是提供一个实用程序来从 Visual Studio 中执行整个测试套件。这通常是运行持续集成工具（例如从 CruiseControl 启动的 NUnit）的构建服务器或测试套件服务器的目标。Resharper
单元测试运行程序似乎最好通过运行少量单元测试来诊断和满足特定的代码单元。它允许您创建有针对性的测试套件，可以在工作室内方便地运行、快速调试、重复和分析，而无需等待构建。
我建议利用构建服务器来运行完整的测试套件。
I don't think the goal of Resharper was to provide a utility to execute an entire test suite from within Visual Studio. That is usually the goal of a build server or test suite server running continuous integration tools (like NUnit launched from CruiseControl)
The Resharper unit test runner appears best leveraged by running small sets of unit tests to diagnose and satisfy a particular unit of code. It allows you to create focused test suites that can be conveniently run from within the studio, debugged, repeated, and analyzed quickly without waiting for builds.
I would recommend leveraging a build server for running the complete suite of tests.