公共类TestClass：IDisposable{公共无效处理（）{}}

            

             
(TestClass］公共类夹具{公共接口它{} [TestMethod］公共异步任务测试（）{ITest mock = mock . create ();使用TestClass test =新（）;}}
            

(TestMethod］公共无效TestMethod（）{varcultureInfo = Mock.Create< cultureInfo >();varthisThrowsAnException = cultureInfo.Name;}

一种可能的解决方法是创建一个这样的模拟:

            

             
只读的字符串cultureName = CultureInfo.InvariantCulture.Name;…varcultureInfo = Mock.Create(() =>新CultureInfo (cultureName));
            

000000CD7CE038D0 00007ffafb22d3b6 [GCFrame: 000000CD7CE038D0] 000000CD7CE03A40 00007ffafb22d3b6 [PrestubMethodFrame: 000000cd7ce0a40] 000000CD7CE0A530 00007ffafb22d3b6 [PrestubMethodFrame: 000000CD7CE0A530] System.Runtime.Loader.AssemblyLoadContext.OnAssemblyResolve(System.Reflection. System.Reflection.)RuntimeAssembly, System.String) 000000CD7CE0A988 00007ffafb22d3b6 [GCFrame: 000000CD7CE0A988] 000000CD7CE0E3C0 00007ffafb22d3b6 [PrestubMethodFrame: 000000CD7CE0E3C0] System.Runtime.Loader.AssemblyLoadContext.OnAssemblyResolve(System.Reflection. string)RuntimeAssembly, System.String)…(为简洁而省略)000000CD7CF72548 00007ffafb22d3b6 [GCFrame: 000000CD7CF72548] 000000CD7CF75F80 00007ffafb22d3b6 [PrestubMethodFrame: 000000CD7CF75F80] System.Runtime.Loader.AssemblyLoadContext.OnAssemblyResolve(System.Reflection. System.Reflection.)RuntimeAssembly, System.String) 000000CD7CF763D8 00007ffafb22d3b6 [GCFrame: 000000CD7CF763D8] 000000CD7CF79E10 00007ffafb22d3b6 [PrestubMethodFrame: 000000CD7CF79E10] System.Runtime.Loader.AssemblyLoadContext.OnAssemblyResolve(System.Reflection. System.Reflection.)RuntimeAssembly, System. string) 000000CD7CF7A268 00007ffafb22d3b6 [GCFrame: 000000CD7CF7A268] 000000CD7CF7DCA0 00007ffafb22d3b6 [PrestubMethodFrame: 000000CD7CF7DCA0] System. collections . general . dictionary ' 2[[System. collections . general . dictionary]__Canon, System.Private.CoreLib]、[系统。__Canon, System. private . corelib]]..ctor() 000000CD7CF7DF10 00007FFA9B787B2A System. appcontext .cctor() [/_/src/System. private . corelib /shared/System/AppContext.cs @ 16] 000000CD7CF7E340 00007ffafb2b6c93 [GCFrame: 000000CD7CF7E340] 000000CD7CF7ED18 00007ffafb2b6c93 [HelperMethodFrame: 000000CD7CF7ED18] 000000CD7CF7EE20 00007FFA9B7876B9 System. appcontext . cn]设置(Char**， Char**， Int32)

公共接口IMyInterface{intIntProperty {得到= >0;}} [TestClass］公共类UnitTest1{(TestMethod］公共无效TestMethod1（）{varmock = mock . create ();Mock.Arrange(() => mock.IntProperty). return (1）;断言。AreEqual (1, mock.IntProperty);}}

公共类Class1{私人字符串__arg1;公共Class1（字符串__arg1）{这.arg1 = arg1;}公共类别3方法（字符串参数）{扔新NotImplementedException ();}}公共类类别2{静态Class3 class3Instance;公共静态无效StaticMethod（字符串__arg1、字符串最长）{Class1 class1Instance =新Class1 (__arg1);class3Instance = class1Instance.Method(arg2);}}公共类类别3{} [TestClass］公共类Class2Test{静态Class1 mockClass1 = Mock.Create();mockClass3 = Mock.Create();(TestInitialize］公共无效设置（）{Mock.Arrange(() =>新Class1 (“__arg1”) .Returns (mockClass1);Mock.Arrange(() => mockClass1。方法(“最长”) .Returns (mockClass3);} (TestMethod］公共无效的（）{Class2。StaticMethod (“__arg1”，“最长”）;}}

测试通过了，但调试跟踪输出包含警告消息:从另一个测试方法调用一个测试方法可能会导致意外的行为，必须避免。从一个非测试方法中提取通用的模拟逻辑。”甚至没有调用其他测试方法。

使用Azure.Messaging.ServiceBus;公共类类别2{私人静态ServiceBusSender messageToTopicSender;私人静态字符串topicName;公共静态无效SetRequestTopicClient（字符串serviceBusConnectionString,字符串topName）{topicName = topName;ServiceBusClient =新ServiceBusClient (serviceBusConnectionString);messageToTopicSender = serviceBusClient.CreateSender(topicName);}}

下面的测试

            

             
(TestClass］公共类Class1Test{(TestInitialize］公共无效设置（）{Mock.Arrange(() => Class2。SetRequestTopicClient (”“，”“) .DoNothing ();} (TestMethod］公共无效外种皮（）{Class2。SetRequestTopicClient (”“，”“）;}} [TestClass］公共类Class2Test{静态ServiceBusClient = Mock.Create();messageToTopicSender = Mock.Create();(TestInitialize］公共无效设置（）{Mock.Arrange(() =>新ServiceBusClient (“若干”) .Returns (serviceBusClient);Mock.Arrange(() => serviceBusClient。CreateSender (“myTopic”) .Returns (messageToTopicSender);} (TestMethod］公共无效的（）{Class2。SetRequestTopicClient (“若干”，“myTopic”）;}}
            

按照TestA -> TestB的顺序执行测试会导致TestB失败，但更改顺序或单独运行测试会成功。测试的结果不应该依赖于执行顺序。