| CATEGORIES |
|
| DEVELOPER AREA |
|
| FREE NEWSLETTER |
|
Join our free e-mail newsletter to receive news of the
latest releases.
|
|
 |
|
Home /
Software Developer / Debugging
Fault Factory v1.0
| Author: |
ExtraData Technologies |
| Platform: |
Windows (all) |
| Price: |
$179 |
| Submitted: |
02/11/2006 |
| File Size: |
1000 KB |
| Downloads: |
265 |
| Rating: |
 |
|
|
 |
Can your application fail under some random network condition that is hard to reproduce under debugger?
Fault Factory allows to create a variety of socket or HTTP/SOAP faults in any running application with no compile-time instrumentation or system changes. Your app can receive a variety of hard-to-reproduce faults -- is it ready? Fault factory lets you easily reproduce conditions such as SOAP Faults, HTTP error codes, various socket-level communication faults (dropped/refused connections, buffer problems, timeouts, etc.)
The package contains a GUI Console and an Agent. The Agent dynamically attaches to a running application - no special configuration or system changes required. The Console allows configuring agent actions globally or on a per-call basis
In interactive mode, the Console reports a 'breakpoint' on the given call, allowing the developer to configure the response they want. It is also possible to configure random responses -- useful to create a broad test with minimal effort
Fault Factory is implementation-neutral and can inject faults into any Windows application, regardless of the implementation language: Java, Perl, Python, C/C++, any .NET (e.g. C#)
Fault Factory can co-exist and inter-operate with standard IDEs and debugging tools, such as Eclipse, NetBeans and Microsoft Development Environment. For example, you can put a breakpoint in Eclipse on a call that can throw a network-related exception, then configure Fault Factory to fail the next call. Stepping over the call in Eclipse, will throw the exception needed
|
See also:
|
|
