Fault Factory

Fault Factory - Inject HTTP/SOAP/Socket faults into your application - no code changes, no proxies!
Download

Fault Factory Ranking & Summary

Advertisement

  • Rating:
  • License:
  • Free to try
  • Price:
  • $179.00
  • Publisher Name:
  • ExtraData Technologies
  • Operating Systems:
  • Windows 2000, Windows XP
  • File Size:
  • 1,001.87K

Fault Factory Tags


Fault Factory Description

Fault Factory was designed to be a unique active debugging solution for applications that communicate with other applications over the network. Fault Factory uses API-Level Fault Injection to imitate faults and exercise error-handling code Your code may be calling a method that can return an error or throw an exception under some circumstances. The set of circumstances that generate the error condition may be rare, and it may be difficult to encounter during product development, but nevertheless error conditions do occur during the real-life use of your application, and therefore need to be tested For example, you may periodically get ENOBUF error from many socket calls, even under normal use. Or you may sometimes receive ECONNABORTED or ENETDOWN. It may be very difficult to reproduce those conditions without Fault Factory, but your code should be ready to receive them at any moment... Fault Factory injects two types of faults: socket API failures and arbitrary HTTP responses (that can be used to imitate a wide range of conditions, including SOAP faults) Ensuring a networked application behaves correctly under a variety of real-life conditions present a challenge. There are numerous faults that can happen at any moment, but they are usually hard-to-reproduce Many faults just do not happen on a developer's machine or on a healthy network, but they do happen often enough under real-life conditions. If your application is not ready to handle a fault, it can be very damaging. Fault Factory allows a developer or tester to reproduce those conditions at will. It allows to create a variety of socket or HTTP/SOAP faults in any running application Application programmers often use system or 3rd party libraries that provide an abstraction layer on top of the network. Unfortunately, the libraries themselves may introduce behavior that is not intended, such as repeating a failing call too fast, causing your application to hog the system resources. It is also possible that those libraries can have bugs in handling specific conditions, since negative testing is quite often neglected or trivialized


Fault Factory Related Software