title: How do you intentionally cause a SoapFault for testing?
body: <p>I implemented a SoapClient interface for handling rate requests to the Federal Express Rate request web services. Last night at around 1 am the system was returning soap fault conditions that my code handled with it's response checking (it basically skips over and sends a generic message if it doesn't find a valid rate response) but which isn't handled specifically.</p>
  
  <p>When the service itself is down, I would like to show a more useful message to customers specifically for such faults when the remote services are actually down to perhaps cut down the calls to our tech support. (the generic message says 'try again later', but if I know it's specifically a problem with the FedEx services being down, I can say 'FedEx Rate Service temporarily unavailable' so people will know it's not our site, but theirs)</p>
  
  <p>I've already implemented code to handle a SoapFault condition, but now I have the problem of 'how to test it' as the FedEx rate service was only down briefly last night.</p>
  
  <p>Is there a way to intentionally trigger a soap condition, perhaps even specific soap fault for testing purposes?</p>