Package org.apache.solr.common.util
Class CommonTestInjection
java.lang.Object
org.apache.solr.common.util.CommonTestInjection
Allows random faults to be injected in running code during test runs across all solr packages.
- NOTE: This API is for internal purposes only and might change in incompatible ways in the next release.
-
Nested Class Summary
Nested ClassesModifier and TypeClassDescriptionstatic interfacestatic classBreakpoints should be set via thisCommonTestInjection.BreakpointSetterwithin the test case and close should be invoked as cleanup. -
Constructor Summary
Constructors -
Method Summary
Modifier and TypeMethodDescriptionstatic booleaninjectBreakpoint(String key, Object... args) Injects a breakpoint that pauses the existing code execution, executes the code defined in the breakpoint implementation and then resumes afterward.static booleanInject an artificial delay(sleep) into the codestatic voidreset()static voidsetAdditionalProps(Map<String, String> additionalSystemProps) static voidSet test delay (sleep) in unit of milliseconds
-
Constructor Details
-
CommonTestInjection
public CommonTestInjection()
-
-
Method Details
-
reset
public static void reset() -
setAdditionalProps
-
injectAdditionalProps
-
setDelay
Set test delay (sleep) in unit of milliseconds- Parameters:
delay- delay in milliseconds, null to remove such delay
-
injectDelay
public static boolean injectDelay()Inject an artificial delay(sleep) into the code- Returns:
- true
-
injectBreakpoint
Injects a breakpoint that pauses the existing code execution, executes the code defined in the breakpoint implementation and then resumes afterward. The breakpoint implementation is looked up by the corresponding key used inCommonTestInjection.BreakpointSetter.setImplementation(String, Breakpoint)An example usages :
- Inject a precise wait until a race condition is fulfilled before proceeding with original code execution
- Inject a flag to catch exception statement which handles the exception without re-throwing. This could verify caught exception does get triggered
This should always be a part of an assert statement (ie assert injectBreakpoint(key)) such that it will be skipped for normal code execution
- Parameters:
key- could simply be the fully qualified class name or more granular like class name + other id (such as method name). This should only be set by corresponding unit test cases with CommonTestInjection#setBreakpointargs- optional arguments list to be passed to the Breakpoint- See Also:
-