python 3.6中的内联注释行为与2.7不同(Inline comment behavior in python 3.6 different from 2.7)

 你只能模拟虚拟/抽象方法，除非你使用像TypeMock这样的重型东西。 
 
 当您必须测试无法控制的代码时，您将不得不打破对该代码的依赖。 创建一个包含untestable类的方法，属性和事件的Facade。 坚持你实际使用的那些; 它会记住你必须编写的代码的大小。 针对您控制的外观的代码而不是您没有的代码。 
 
 最后一件事是使用几种技术中的一种来访问外观，这将允许您在测试期间替换模拟。 您可以使用配置文件，依赖注入框架，延迟实例化等。这样您就可以模拟您的外观并将其用于单元测试。 当然，您仍然需要进行一些集成测试，以确保您的外观与实际的COM互操作类正常工作。 
 
 要获得一些灵感，请查看System.Web.Abstractions。 它包含许多类，它们包装ASP.NET核心类以使它们可模拟。 

You can only mock virtual/abstract methods, unless you use something heavy-duty like TypeMock. 
 
When you have to test code that you don't have control over, you're going to have to break your dependency on that code. Create a facade that has the methods, properties and events of the untestable class. Stick with the ones that you actually use; it'll keep down on the size of the code you have to write. Code against the facade you control rather than the code you don't.
 
The last thing is to use one of the several techniques to access the the facade that will allow you to substitute a mock during tests. You can use config files, dependency injection frameworks, lazy instantiation, etc. This way you can mock out your facade and use it for unit tests. Of course, you'll still have to do some integration tests to make sure your facade works correctly with the actual COM interop class.
 
For some inspiration, take a look at System.Web.Abstractions. It contains many classes which wrap ASP.NET core classes to make them mockable.