开发者

Fault injection for .NET apps?

开发者 https://www.devze.com 2022-12-20 07:04 出处:网络
I am wondering if anyone knows of tools or techniques to automatically inject common faults into a running .N开发者_StackOverflowET program.Stuff like...

I am wondering if anyone knows of tools or techniques to automatically inject common faults into a running .N开发者_StackOverflowET program. Stuff like...

  • Randomly inject an OutOfMemoryException upon allocation
  • Randomly inject FileNotFoundException upon trying to access a files
  • Randomly inject IO or Network exceptions upon using a socket.

So I'm really looking for a way to intercept some specific calls in the CLR similar to what AppVerifier does for native Win32 code. The purpose is to test apps under lots of error conditions beyond the developers control and to make sure such conditions are handled.


There is a codeplex project called TestAPI that can do runtime fault injection. You need to look at its managed code fault injection API. It uses the CLR profiling API to intercept method calls at runtime and modify their behaviour.

Have a look at an example to see how to inject an exception on a method call in an already compiled exe.


Typemock Isolator seems to be your best bet.

Here's what you can do, if you want to throw a FileNotFoundException to simulate testing.

In your production code, you have such method

public static Project OpenProject(string filePath)

And in your test code, you can fake the OpenProject call like this

Isolate.WhenCalled(()=>Project.OpenProject(nulll)).WillThrow(new FileNotFoundException());

And when your code hit OpenProject, a FileNotFoundException will be thrown.


This isn't exactly on point with what your asking, but it's related and may be helpful toward the same goal of improving exception handling in your app.

redgate Exception Hunter http://www.red-gate.com/products/Exception_Hunter/index.htm

I haven't used this particular product but other redgate products I've used were great.


I don't know how one would "randomly" inject these things, but I would recommend you mock out the part that's not normally under your control, and have the mock throw an exception in some of your tests.

0

精彩评论

暂无评论...
验证码 换一张
取 消