Byteman

It uses a technique called fault injection.

Byteman's scripting language is based on Java, using a formalism called Event Condition Action rules to specify where, whether and what side effects should be executed during a test run. This allows Byteman rules to be powerful and expressive without sacrificing structure, clarity and ease of use.

Byteman works by inserting scripted side effects into application code, Test scripts may include actions which create and propagate conditions appropriate to the test scenario.

What is new in this release:

• Feature Request:
• Provide rendezvous with timeout to avoid deadlock in tests
• Bugs:
• "Obtaining the sources" and "Building Byteman" sections of documentation are incorrect
• Dtest library does not know to work with interfaces
• Dtest library does not know to instrument overloaded methods
• Enhancement:
• Added a @BMUnitConfig annotation for configuring agent from unit test

What is new in version 3.0.1:

• Feature Request:
• Provide rendezvous with timeout to avoid deadlock in tests
• Bugs:
• "Obtaining the sources" and "Building Byteman" sections of documentation are incorrect
• Dtest library does not know to work with interfaces
• Dtest library does not know to instrument overloaded methods
• Enhancement:
• Added a @BMUnitConfig annotation for configuring agent from unit test

What is new in version 2.2.2:

• Feature Request:
• Provide rendezvous with timeout to avoid deadlock in tests
• Bugs:
• "Obtaining the sources" and "Building Byteman" sections of documentation are incorrect
• Dtest library does not know to work with interfaces
• Dtest library does not know to instrument overloaded methods
• Enhancement:
• Added a @BMUnitConfig annotation for configuring agent from unit test

What is new in version 2.2.1:

• Feature Request:
• Provide rendezvous with timeout to avoid deadlock in tests
• Bugs:
• "Obtaining the sources" and "Building Byteman" sections of documentation are incorrect
• Dtest library does not know to work with interfaces
• Dtest library does not know to instrument overloaded methods
• Enhancement:
• Added a @BMUnitConfig annotation for configuring agent from unit test

What is new in version 2.1.4.1:

• Loading rules script file with ClassLoader .getSystemResourceAsStream("bytemanpkg.btm");

What is new in version 2.1.0:

• Features:
• Support length property for array types
• Enhance Instrumentor.class of dtest to be more flexible
• Fixed Bugs:
• Missing spaces in output
• VerifyError under JDK7

What is new in version 2.0.3:

• Added helper to trace stacks of other threads.
• Deploy Byteman release to maven central.

What is new in version 2.0.1:

• Enhancements:
• Improved trigger injection to disable injection for methods which fail to match a rule while allowing others cases to proceed.
• Features:
• Search for 'value' and 'dir' on the classpath as well.
• Added Windows equivalents for Linux/bash command scripts to release bin directory.

What is new in version 1.3.0:

• Feature Requests:
• Provide rule bindings for a method parameters array and a method parameter count
• Allow access to stack content in AT INVOKE rules
• Add call stack util methods to default helper
• Provide lifecycle management for rules/helpers
• Contribute dtest prototype
• Can locations which take a count also take keyword ALL
• Provide -p flag to bytemancheck script allowing packages for rule classes to be specified
• It should be possible to redefine the default helper per script
• Bugs:
• Compiler fails to call toString to convert a Numeric object type to a String
• AT ENTRY rules are being executed in reverse order of presentation contrary to spec
• StringLiteral TypeCheck is not throwing an error if it is passed an incompatible expected type
• Local var frame management in generator adapter is failing to account for some local vars
• Transformer is allowing injection to be attempted on native methods
• AT ENTRY rules injected into methods starting with a while loop can end up inside the while
• Open monitor enter propagation algorithm in CFG is broken
• Type checker fails to allow boxed primitive types to be employed where a super type is expected
• NumericLiteral typecheck is not allowing numeric literal to appear where an object is expected
• Setting the helper in one rule leaves it set for later rules
• Submit is no longer respecting script ordering
• Tasks:
• Upgrade junit to 4.8.2

Requirements:

• JDK 6 or higher