In almost all situations it’s pointless to test code paths that result in unhandled exceptions, they’re by definition exceptional and unhandleable. This would be akin to trying to make code that uses File.ReadAllText throw an exception for a damaged sector on a hard drive. Is it remotely feasible you COULD do it? Yes. Will you gain anything? No. The only reason you would ever do something like that is if you are testing code to be tolerant of the exceptions. Like backup software, you probably want it to handle every kind of disk error possible and at the end display what failed instead of abandoning it in the middle.