IDE 在抛出 AssertionException 时停止，而不是测试失败。（MSTestExtensions 的罪魁祸首？）

发布于 2024-09-27 02:49:08 字数 1284 浏览 6 评论 0原文

我在 MSTest 项目中使用 NUnit 断言，如下所示（注意：这应该不重要，请参阅 Dave Falkner 的答案的评论）：

using Microsoft.VisualStudio.TestTools.UnitTesting;
using MSTestExtensions;
using Assert = NUnit.Framework.Assert;
using Is = NUnit.Framework.Is;

这在我的单元测试中效果很好，但在我的集成测试中我我遇到了一些麻烦。我认为这可能是由于 MSTestExtensions 造成的，因为我的单元测试没有使用它。此外，如果我注释掉 MSTestExtensions using 语句、类上的继承 MSTestExtensionsTestFixture 语句以及 [TestTransaction] 属性，我就不会遇到此问题。重新添加 using 语句不会导致问题。添加 [TestTransaction] 属性不会导致问题。一旦我从测试类上的 MSTestExtensionsTestFixture 继承，问题就会出现。

基本上，问题在于，当我在失败的情况下执行以下代码时（例如，actualPartNumbers 列表包含两个部分，而预期列表仅包含一个部分），MSTest 不会处理 AssertionException。

Assert.That(actualPartNumbers, Is.EquivalentTo(expectedPartNumbers));

因此，IDE 在抛出异常时停止，而不是测试失败。有时这种情况不会发生，测试会正常失败。但在大多数情况下，IDE 会在抛出异常时停止。有什么想法吗？

仅供参考： 我正在使用 MSTestExtensions，以便我可以在每次测试后执行数据库回滚（[TestTransaction] 属性）。这与 MbUnit 的回滚功能类似。我用 NUnit 覆盖 MSTest 的断言，因为我更喜欢流畅的风格。最后，我使用 MSTest 因为我在使用 NUnit 时遇到问题。特别是对于 Microsoft Moles 和与使用 log4net 的第三方引用发生冲突。我正在尽力设置单元/集成测试，以便在我切换时能够在任一框架中运行。但就目前而言，MSTest 似乎是最不麻烦的，并且在 IDE 中的集成非常好。

原文

I am using NUnit asserts within a MSTest project like as follows (NOTE: This shouldn't matter see comments to Dave Falkner's answer):

using Microsoft.VisualStudio.TestTools.UnitTesting;
using MSTestExtensions;
using Assert = NUnit.Framework.Assert;
using Is = NUnit.Framework.Is;

This has worked great in my unit tests, but in my integration tests I am having some trouble. I think it might be due to MSTestExtensions as my unit tests were not using it. Additionally, if I comment out the MSTestExtensions using statement, the inherit MSTestExtensionsTestFixture statement on the class, and the [TestTransaction] attribute, I don't have this problem. Adding the using statement back in doesn't cause the problem. Adding the [TestTransaction] attribute doesn't cause the problem. Once I inherit from MSTestExtensionsTestFixture on the test class, the issue presents itself.

Basically, the problem is that when I execute the following code in a situation that it will fail (such as the actualPartNumbers list containing two parts, whereas the expected list contains only one), the AssertionException goes unhandled by MSTest.

Assert.That(actualPartNumbers, Is.EquivalentTo(expectedPartNumbers));

Thus the IDE stops at the thrown exception, rather than fail the test. Sometimes this doesn't happen and the test will fail normally. But in most cases the IDE stops at the thrown exception. Any ideas?

FYI:
I'm using MSTestExtensions so that I can do database rollbacks ([TestTransaction] attribute) after each test. This is similar to MbUnit's rollback feature. I'm overriding MSTest's asserts with NUnit's because I like the fluent style better. Lastly, I'm using MSTest because I'm having issues with NUnit. Particularly with Microsoft Moles and conflicts with third party references that use log4net. I'm trying my best to setup the unit/integration tests to be able to run in either framework in case I switch. But for now MSTest seems to be the least hassle and the integration in the IDE is very nice.

分享到QQ

分享到微博